Summary: | Persistent encoding error message in Advanced Editor | ||
---|---|---|---|
Product: | Koha | Reporter: | Esther Melander <esther.melander> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | david, lauren_denny, m.de.rooy, phil |
Version: | 23.05 | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34014 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35184 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: | Record with encoding errors? |
Hi Esther. Thanks for providing a sample record! I had a go at testing the sample record you provided in Koha 23.05.05. I didn't encounter any errors importing, viewing, or editing with the standard and advanced editor (apart from needing to change 942$c). Tested using koha-testing-docker (KTD). David Hi Esther, this sounds like a duplicate of Bug 35181 - Can no longer edit sample records with advanced cataloguing editor. Have you been testing in a version lower than 23.05.06? I was using 23.05.05. I tried editing the example record again this morning and the persistent warning message is now gone. Could there be some kind of caching happening? If it helps, I use the Brave browser. I believe this is likely connected to Bug 35181. |
Created attachment 159376 [details] Record with encoding errors? Related to bugs 34014 and 351814 Recreating this bug requires having a record with some kind of encoding error. Usual errors included bad characters or record separator characters such as blank spaces. My understanding of the bug fixes above are that the fix should automatically strip out the errors. The encoding error notification should only appear one time. 1. Find record with errors (example record attached that has a persistent error message). 2. Open record in the advanced editor. 3. See the encoding error notification. Click on it to make it go away. 4. Edit the record in some way. 5. Save the record and close the advanced editor. 6. Reopen the record in the Advanced editor and see the encoding warning box again. No encoding error message appears when opening the record in the Basic Editor. Also if we tell the user to check the logs, there should be a convenient way to access them - which perhaps is a separate issue.