Using the Contextual Preferences Engine, this moves the following preferences out of Sysprefs and down to the per-branch level. LibraryName OPACBaseURL opaccolorstylesheet opaccredits opacheader opaclayoutstylesheet OpacMainUserBlock OpacNav OPACNoResultsFound opacsmallimage opacstylesheet OPACUserCSS opacuserjs
The Contextual Preferences Engine?
Regarding branch specific CSS in Opac we could do the following: 1) Add a class="branchcode" to the body tag using the branch code, i.e something like <body id="opac-main" class="CPL"> 2) Using this class, we could style branch specific pages e.g. in OPACUserCSS: /*Background for all branches*/ body { background-color: red; } /*Yellow background and pink border for branch with code CPL*/ body.CPL { background-color: yellow; border: 10px solid pink; } /*Green background and red border for branch with code CPL*/ body.FFL { background-color: green; border: 10px solid red; } ...or a lot of other branch specific things like background images etc.
(In reply to Owen Leonard from comment #1) > The Contextual Preferences Engine? Regarding the Contextual Preferences Engine I found the following thread: http://lists.katipo.co.nz/public/koha/2012-March/032347.html
(Regarding comment #2) I moved the idea with branch specific CSS in a separate bug. 12162
Currently one option to achieve this is overwriting system preferences from Apache. I am not sure if the 'contextual preferences engine' is going to happen at this point in time, as the developer has left. Maybe we could reuse this bug to improve the 'different OPAC views' idea, that can currently be only achieved with Apache settings. I think we need a concept for this, before moving the preferences makes sense.
> opaccredits > opacheader > OpacMainUserBlock > OpacNav > OPACNoResultsFound But 22318 enables fixes for these preferences.