http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13291 --- Comment #12 from Indranil Das Gupta <indradg@gmail.com> --- (In reply to Katrin Fischer from comment #10)
Hm, thinking about this, you are probably right. If you have your own set of templates, hardcoding the fallback to the only available OPAC template seems right. OTH if we want to allow people to add other fallbacks and avoid changing files in Koha, this should not be a pull down but a text field?
Sounds like a fair argument - like say bootstrap|prog|custom_theme_name The ordering of these could then drive the selection in C4::Templates::themelanguage() Not that it would address Tomas's observation in line 243 about the hardcoding in case of an unpopulated db -- You are receiving this mail because: You are watching all bug changes.