#39 XML parser error if & used in page field

[Marc Kupper]

If an editor submits a publication where something like "9 & 10" are used in the page field for a Contents item then
1) The New Submissions queue shows a Submitter of "ERROR" in bold and a Subject of "XML PARSE ERROR" also in bold.

2) If you click through to view the submission the display starts out with a red box that states "Error: Badly formed XML" and is followed by the XML blob where you can see <cPage>9 & 10</cPage> rather than the expected <cPage>9 &amp; 10</cPage>. An example of this is http://www.isfdb.org/cgi-bin/mod/pv_update.cgi?1073817

3) For some submissions, you get a Python "explosion" when you try to view the submission. http://www.isfdb.org/cgi-bin/mod/cv_new.cgi?1081094 is an example of this. I've attached this as a text file.

Note that neither submission should be approved. The first has already been handled with other updates and the latter was to replicate this issue.

[Marc Kupper]

Python error for submission 1081094

[Ahasuerus]

The problem submission reported above had an unescaped ampersand in its body. When I tried to enter an ampersand in the page field earlier today, it was properly escaped when added to the submission queue and there was no error. Closing as out of date.

[Ahasuerus]

The problem can be reliably recreated by entering an ampersand in the Page *number* field in the Content section rather than in the Page Count field at the Publication level.

[Ahasuerus]

Fixed in common/puvClass 1.8.

[Ahasuerus]

Implemented in r2009-47.