| Summary: | Be able to configure HTML Opac preferences per library | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Nicole C. Engard <nengard> |
| Component: | System Administration | Assignee: | Bugs List <koha-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | new feature | ||
| Priority: | P5 - low | CC: | gmcharlt, jsasse, lisette, marjorie.barry-vila, verolencinas, veron |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8067 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22318 |
||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Nicole C. Engard
2013-11-14 15:50:22 UTC
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
|