Bug 16712 - Unknown Error Message from Item records
Summary: Unknown Error Message from Item records
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 3.18
Hardware: All All
: P5 - low normal
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
: 16713 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-06-11 00:33 UTC by Laura
Modified: 2017-06-14 22:07 UTC (History)
1 user (show)

See Also:
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

Note You need to log in before you can comment on or make changes to this bug.
Description Laura 2016-06-11 00:33:33 UTC
Hi, 
  I'm running Koha 3.18.12.000 and I can this error when I try to update items for a record: 

:21: parser error : Opening and ending tag mismatch: record line 6 and datafield 
</datafield>
            ^ 
:22: parser error : Opening and ending tag mismatch: collection line 2 and record 
</record>
         ^ 
:23: parser error : Extra content at the end of the document 
</collection>

the url pattern is something like this: 
../cgi-bin/koha/cataloguing/additem.pl?op=edititem&biblionumber=''&itemnumber=''#edititem 

When I edit one of the fields on this screen it throughs the error above.  It seems like a xml error, but after some internet sleuthing I came up with nothing.  I also posted to the boarded and waited at least a month for a response and found nothing.  The error message doesn't tell me much about wha the error is.
Comment 1 Owen Leonard 2016-06-21 11:35:31 UTC
*** Bug 16713 has been marked as a duplicate of this bug. ***
Comment 2 Owen Leonard 2016-06-21 14:17:42 UTC
Does this error happen with all records, or just one? I don't have 3.18.12, but other versions of 3.18.x have no problems.

It sounds like it might be in issue with corrupt data.
Comment 3 Katrin Fischer 2016-08-14 15:22:35 UTC
We have been using 3.18 for a long time now with our libraries without experiencing this error. I think it might be related to invalid data - as it sounds like an error in the MARCXML.

Laura, please reopen, if you still experience the problem.