We've discovered that leading whitespaces in at least the 947h field have caused error messages on bib records (detail.pl), and lists linked to the record to fail to load (shelves.pl). Perhaps there should be something in place to either warn or automatically strip leading/trailing whitespaces on these fields, or something done to prevent these whitespaces from breaking things.
All good for me. Which Koha versions? Which errors in the koha logs? In the JS console? Can you attach the record to this bug report?
(In reply to Jonathan Druart from comment #1) > All good for me. Which Koha versions? Which errors in the koha logs? In the > JS console? Can you attach the record to this bug report? Right now we are seeing this in 19.05. I don't know about earlier versions. The records were repaired, so I don't have an example at the moment. I will see if I can recreate this manually.
(In reply to Jonathan Druart from comment #1) > All good for me. Which Koha versions? Which errors in the koha logs? In the > JS console? Can you attach the record to this bug report? I can't manually recreate this, but I am checking with Bywater to see if they can. I am suspecting the whitespace was transferred through a downloaded record, since I can't manually create the error. Wonder if there needs to be something in place to strip leading whitespace on downloaded records?
No, edit a record, add trailing/leading whitespaces, save, edit again => Whitespaces are still there.
(In reply to Jonathan Druart from comment #4) > No, edit a record, add trailing/leading whitespaces, save, edit again > => Whitespaces are still there. This isn't a matter of manually adding whitespace. I can do that. It just isn't creating the same effect. So, there is something more specific about the whitespace that I don't know about.
(In reply to Christopher Brannon from comment #5) > (In reply to Jonathan Druart from comment #4) > > No, edit a record, add trailing/leading whitespaces, save, edit again > > => Whitespaces are still there. > > This isn't a matter of manually adding whitespace. I can do that. It just > isn't creating the same effect. So, there is something more specific about > the whitespace that I don't know about. Maybe it was not whitespace but some other non-printable characters that got in fro copy&pasting?