Summary: | Unimac plugin 225$a error 500 | ||
---|---|---|---|
Product: | Koha | Reporter: | Chris Cormack <chris> |
Component: | Cataloging | Assignee: | Henri-Damien LAURENT <henridamien> |
Status: | CLOSED FIXED | QA Contact: | Bugs List <koha-bugs> |
Severity: | enhancement | ||
Priority: | PATCH-Sent (DO NOT USE) | CC: | f.demians, frederic.durand, paul.poulain, stephane.delaune |
Version: | rel_3_2 | ||
Hardware: | PC | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: | Patch new plugin 210c |
Description
Chris Cormack
2010-05-21 01:13:01 UTC
This plugin won't work without a 'special' and undocumented authority type EDITORS populated by buildEDITORS.pl script, or by hand. This patch allows this plugin (and 210 related) to work properly: http://lists.koha-community.org/pipermail/koha-patches/2010-June/012113.html You can close this bug as soon as this patch will be applied. We have submitted a new 210c plugin, and I think EDITORS "authorities" should be deprecated (the collection 225 plugin still has no replacement, and I think we should build something over seriestitle Koha field > We have submitted a new 210c plugin, and I think EDITORS "authorities" > should be deprecated (the collection 225 plugin still has no > replacement, and I think we should build something over seriestitle > Koha field Yes, I can see a patch for a new 210c plugin: http://lists.koha-community.org/pipermail/koha-patches/2010-December/013369.html http://lists.koha-community.org/pipermail/koha-patches/2010-December/013371.html I can apply those patches but the new 210c plugin doesn't seem to work. Created attachment 3730 [details] [review] Patch new plugin 210c Some errors was presents in precedents patches. This path works for me. Initial bug with 225$a is no longer a problem, no more error 500 when clicking. Last patch about 210$c is much more relevant for Bug 3626, will be pushed there so. Whats the status of this ? > Whats the status of this ?
The plugin works on HEAD (3.4)
So we can mark it resolved, or does it still need a patch pushed? |