LOVD 2.0

Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!

If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.

Information By default, all closed tasks are hidden from view.
Click here to see all tasks.

Tasklist

FS#57 - Unescaped ampersands in XML output

Attached to Project: LOVD 2.0
Opened by Adam Webb (adamwebb) - Tuesday, 03 July 2012, 17:43 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Thursday, 21 February 2013, 15:26 GMT+2
Task Type Bug Report
Category Other
Status Closed
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Medium
Priority Normal
Reported Version 2.0-34
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

XML feeds can produce invalid output, notably by including unescaped ampersands (&).

Example gene feed:
<?xml version="1.0" encoding="ISO-8859-1"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>TSC2</title>
<link rel="alternate" type="text/html" href="http://chromium.liacs.nl/LOVD2/TSC/home.php?select_db=TSC2"/>
<id>tag:chromium.liacs.nl,2005-01-24:TSC2</id>
<author>
<name>Dr. Johan T. den Dunnen</name>
</author>
<contributor>
<name>Sue Povey & Rosemary Ekong</name>
</contributor>
<published>2005-01-24T00:00:00+01:00</published>
<updated>2012-07-02T16:34:29+02:00</updated>
<content type="text">
id:TSC2
entrez_id:7249
symbol:TSC2
name:Tuberous sclerosis 2
chromosome_location:16p13.3
position_start:chr16:2097990
position_end:chr16:2138712
refseq_genomic:NG_005895.1
refseq_mrna:NM_000548.3
refseq_build:hg19
</content>
</entry>

The ampersand in root>entry>contributor>name should be escaped. Unescaped ampersands can defeat XML parsers :(
This task depends upon

Closed by  Ivo F.A.C. Fokkema (ifokkema)
Thursday, 21 February 2013, 15:26 GMT+2
Reason for closing:  Fixed
Additional comments about closing:  Just released 2.0-35, which includes this fix.
Comment by Ivo F.A.C. Fokkema (ifokkema) - Wednesday, 04 July 2012, 10:27 GMT+2
  • Field changed: Percent Complete (0% → 100%)
Thank you for your report. This is fixed for the next release of LOVD 2.0, but since I'm not sure yet when that'll be, I've installed this fix on all our servers.
Comment by Adam Webb (adamwebb) - Wednesday, 04 July 2012, 17:31 GMT+2
Thanks Ivo. The fix is working.

Loading...