Summary: | Can't call method "subfield" on an undefined value at Biblio.pm (sub _AddBiblioNoZebra) | ||
---|---|---|---|
Product: | Koha | Reporter: | Marc Véron <veron> |
Component: | Cataloging | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | chris, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8301 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Marc Véron
2012-06-23 08:12:13 UTC
Yes, the preference should be removed. It has been deprecated for a while, the only reason it hasn't been removed is that if someone has it set in the db, once you remove it, they can't easily switch it back to zebra. (Unless they know to use the localuse tab) But it should definitely be removed, and no time should be invested in making nozebra work again. What about a warning section e.g. on the page "About Koha" similar to "Server Information", where such things could be indicated? It would test for configuration glitches and show messages like: Warning: "Deprecated System preference 'NoZebra' set. I can imagine that there are other things that could be addressed this way as well. Marking as WONTFIX. A patch to alert people if they have NoZebra has already been submitted. |