Export problem “parsing error”
-
Hi, I decided to export my blog to have a backup on my Mac.
The xml file that gets downloaded to my desktop returns this message when I try to open it with my browser (same thing happens in both Firefox and Flock)XML Parsing Error: undefined entity
Location: file:///Users/bobleckridge/Desktop/wordpress.2007-05-05.xml
Line Number 472, Column 57:<wp:comment_author>Stirling Castle and Wallace Monument « Heroes Not Zombies</wp:comment_author>
——————————————————–^What am I doing wrong?
-
Not 100% sure but my money is on it not liking the term “wp:comment_author” I doubt that that’s defined in XML as it’s wordpress specific. (WordPress calls it WordPress eXtended RSS or WXR)
I always use ultraedit myself when I open up one of these files although that’s not a *.xml reader.
-
I have the same error with all browsers :
XML Parsing Error: undefined entity Location: file://....wordpress.2007-07-20.xml Line Number 9347, Column 46:Voici la raison qu'en a donné Mel Gibson : « Yucatek still has this wonderful, ancient poetry to it that worked fine, it was readily available and had people who could speak it and many of the K'iche' and Itza' people speak Yucatek. »</wp:comment_content> ---------------------------------------------^Cause : HTML entities – here
«– are not accepted by XML.Could this kind of parsing error make the import of my XML-backup in another blog impossible ?
-
It is not meant to be opened up with a browser because it is a specific WordPress Extended RSS formatting. If it was made out of WordPress 2.1.+ or wordpress.com blogs, there is no reason to think it wouldn’t be ok when you import it into another blog.
Trent
-
Thank you. I tried opening it up with a browser only in order to verify my backup. Naturally I can open it in a text editor, but it is less beautiful :-)
-
You can always grab a ‘backup’ blog here at wordpress.com and try importing it to be sure ;)
Trent
-
- The topic ‘Export problem “parsing error”’ is closed to new replies.