EPrints Technical Mailing List Archive

Message: #01856


< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: XML entity error


I need to defer that to Soton!

 

Mark

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Matthew Brady
Sent: Thursday, 18 April 2013 2:04 PM
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: XML entity error

 

This might be a Tim level question… J

 

Would this LibXML2 problem cause the upgrade process to fail in any other ways (that I might not have picked up in logs), due to being unable to handle the XML files correctly ??

Should I re-sync all the data/reload database with 3.1.2 version and run the entire process again?

 

Thanks again for the pin point link to cause

 

Matt

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Mark Gregson
Sent: Thursday, 18 April 2013 1:15 PM
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: XML entity error

 

Matthew’s right in general however EPrints does defines the entities.  The problem is more likely the libxml2 problem described here http://www.eprints.org/tech.php/17105.html

 

Cheers

Mark

 

Mark Gregson | Applications and Development Team Leader
Library eServices | Queensland University of Technology
Level 3 | R Block | Kelvin Grove Campus | GPO Box 2434 | Brisbane 4001
Phone: +61 7 3138 3782 | Web:
http://eprints.qut.edu.au/
ABN: 83 791 724 622
CRICOS No: 00213J

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Matthew Kerwin
Sent: Thursday, 18 April 2013 12:56 PM
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: XML entity error

 

For what it’s worth, the first error message is correct.  Without any DTDs, &nbsp; is not a valid XML entity (it’s a HTML entity.)  You can use &#160; if you don’t want to write/include a HTML-compatibility DTD.

 

--

Matthew Kerwin  |  QUT Library eServices  |  ph 3138 3910  |  matthew.kerwin@qut.edu.au

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Matthew Brady
Sent: Thursday, 18 April 2013 12:38
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] XML entity error

 

Hi All, 

 

I am in the process of upgrading eprints up to 3.3.10 (from 3.1.2), and all seems to have worked so far… database has been upgraded successfully etc., but I’m getting the following error, and I hope someone can tell me where to start looking… It hasn’t occurred in the dev machine, so I’m hoping it’s simply something I missed in migrating from dev to tst.

 

Thanks

 

Matt

 

 

Failed to parse XML file: /opt/eprints3/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined

age or title page. If there are more than four authors, click on the [More&nbsp;

                                                                                ^

Entity: line 396: parser error : Entity 'nbsp' not defined

e page. If there are more than four authors, click on the [More&nbsp;input&nbsp;

                                                                                ^

Entity: line 397: parser error : AttValue: ' expected

<br/>Example: [<span class="ep_form_example">Smith</span>] [<span class="

                                                                         ^

Entity: line 397: parser error : attributes construct error

<br/>Example: [<span class="ep_form_example">Smith</span>] [<span class="

                                                                         ^

Entity: line 397: parser error : Couldn't find end of Start Tag span

<br/>Example: [<span class="ep_form_example">Smith</span>] [<span class="

                                                                         ^

 

 


This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.

The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider of education with the Australian Government.
(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 )


This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.

The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider of education with the Australian Government.
(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 )