| Summary: | can not save item - 500 error message - adding non latin language to public note | ||
|---|---|---|---|
| Product: | Koha | Reporter: | rania.azad |
| Component: | Cataloging | Assignee: | Galen Charlton <gmcharlt> |
| Status: | CLOSED WORKSFORME | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | m.de.rooy |
| Version: | 3.20 | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Crowdfunding committed: | 0 |
| Crowdfunding contact: | Patch complexity: | --- | |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | error 500 | ||
|
Description
rania.azad
2016-02-24 12:59:04 UTC
Hi Rania, I have tried to reproduce the issue on master, but without success. I tried adding public and non-public notes to the items, but no error message appeared. Can you provide a step by step guide with an 'example note' that triggers the problem for you?22 Created attachment 48421 [details]
error 500
Dear Fischer, this is the screenshot of the error that I got when I do add an item for a specific record manually. I do add the date and the call number and barcode into the item as well as a non-latin text to public NOTES then I do save, so the first item is saved but the next item it is not saved and I need to close the browser and log-in again to koha. (I did try all the computers and it is the same issue) (In reply to Katrin Fischer from comment #1) > Can you provide a step by step guide with an 'example note' that triggers > the problem for you? It might be helpful if you could reply with an example of what kind of note triggers the error. Why does the error force you to close the browser? Do your error logs have anything in them which looks relevant? I've added some Arabic script to both internal and public note. Added items one by one and using the multiple feature. I can't reproduce the error on current master. Please reopen if the problem is still present for you and add a test plan with the exact data you are using. |