[Bug 11267] New: default notices should not be allowed to be deleted
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11267 Bug ID: 11267 Summary: default notices should not be allowed to be deleted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs@lists.koha-community.org Reporter: nengard@gmail.com QA Contact: testopia@bugs.koha-community.org I have an error where a new library didn't know what some notices were for so they deleted them. Now if they get a hold and try to print the hold slip they get: Software error: Could not find a letter called 'HOLD_PRINT' in the 'reserves' module at /home/koha/kohaclone/C4/Reserves.pm line 1914. I don't think that any notice that is installed with Koha by default should be allowed to be deleted since they're all there for a reason. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11267 Jonathan Druart <jonathan.druart@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@biblibre.co | |m --- Comment #1 from Jonathan Druart <jonathan.druart@biblibre.com> --- I can imagine some cases where they could be deleted. For instance if you create specific letters for each branch, you don't need the default "all libraries" letters. Or if you want to be sure the letter won't never use. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11267 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I agree with Jonathan - For example there is no other way to turn off the suggestion related notice templates than deleting them. And some notices are not strict about the code - like the overdue notices can really use any code, as long as they are defined in the notice triggers. We'd probably need to make only some non-deleteable. Or have a nicer error message telling the librarian to create a new notice with code X instead of having Koha explode. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org