It would be great to have branch specific opac content. So opacmainuserblock, opacnav, opacnavright, opacnavbottom, opacheader, opaccredits could all be branch specific maybe using a different OPAC customization section in Administration instead of system preferences for these things. Of course one could argue that the entire OPAC preferences section could be broken out in to it's own Admin area - but I'll start small in my suggestion. Nicole
I concur with Nicole. For large consortia, a method to customize the OPAC differently for different branches would be a great addition. George Williams georgew at latahlibrary.org
Workaround: The body tag of OPAC pages contains a class="branch-CPL" (where CPL is the branch code.) You can use that for a CSS trick to show/hide contents depending on the branch. For a proof of concept, put the following into OpacMainUserBlock: <div class="contentCPL" style="display:none;"> <h1> My custom content for CPL</h1> <p>Text for CPL</p> </div> <div class="contentFFL" style="display:none;"> <h1> My custom content for FFL</h1> <p>Text for FFL</p> </div> ...and put the following into OPACUserCSS .branch-CPL .contentCPL { display:block !important; } .branch-FFL .contentFFL { display:block !important; } Switch between branches - the content will appear as appropriate. Marc
This bug could be fixed if we build upon Bug 22318.
*** This bug has been marked as a duplicate of bug 22318 ***