Summary: | 500 Error when a record cannot be displayed | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | Cataloging | Assignee: | Nick Clemens (kidclamp) <nick> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | andrew, jonathan.druart, kyle, m.de.rooy, valerie |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 11175, 28734 | ||
Bug Blocks: | |||
Attachments: | Bug 29970: eval processing of MARC record to avoid crash |
Description
Nick Clemens (kidclamp)
2022-01-28 18:08:26 UTC
This would be much more helpful than the 500 Error. Created attachment 130104 [details] [review] Bug 29970: eval processing of MARC record to avoid crash detail.pl displays a warning at the top of the page when a record contains parsing errors Bug 28734 and bug 11175 added additional parsing of the MARC record, but they did not catch the thrown errors. The existing pattern in the script is to eval responses to avoid crashing This patch wraps the new calls in eval{} To test: 1 - Find a record in the staff catalog 2 - Edit the record 3 - In the 520 notes field, add an ASCII escape character (27 decimal, 1b hex) On ubuntu Ctrl+Shift+u, then 1b, enter 4 - Save the record 5 - 500 Error 6 - Apply patch 7 - Reload 8 - The record displays with a warning at the top I don't understand, we were supposed to have fixed that few days ago, with bug 29690. If the problem still persists, please have a look at the solution there (test $marc_record) |