Home > Xml Parsing > Xml Parsing Error Joomla 1.5

Xml Parsing Error Joomla 1.5

delete every file beginning with "._", especially those ending in ".xml". 3. Forgot your username? Some common causes: a file you have uploaded was uploaded corruptly a component/module/etc you are using has a bad XML file there's some mischief going on... What did John Templeton mean when he said that the four most dangerous words in investing are: ‘this time it’s different'? Source

Error 4: Empty document. You can use muCommander (www.mucommander.com), a filemanager with the good old Norton Commander interface, to open these zip files and delete the "hidden" osx files. Error 4: Empty document", appears to be thrown by routine JSimpleXML::_handleerror(), which is called by JSimpleXML::_parse(), which is a thin wrapper around PHP's xml_parse(), which in turn is a port of Thanks!!!! ----------- # on 15 Apr 2009 at 00:06 Leander Hi, I was also getting these XML parsing errors on my OSX machine and I have a simple solution for it.

mysql 4.1.22-standard PHP 5.2.9 Apache Apache/2.2.11 Joomla Joomla! 1.5.8 Production/Stable mmx Posts: 3Joined: Mon May 25, 2009 9:00 pm Top by IToris team » Wed May 27, 2009 12:16 pm Error 108: Unknown Please ask questions, report bugs and share your ideas about SmartFormer Gold for Joomla in this forum Post a reply 4 posts • Page 1 of 1 SOLVED: Then the method parses the correct templateDetails.xml file to complete the installation.

Draw some mountain peaks Can a PCIe bus exist on its own? Invalid type: JSON.createGenerator Player claims their wizard character knows everything (from books). I don't provide support by PM, because this can be useful for someone else. Accessibility Statement Privacy Policy Gforge

May no-one else have to spend the hours I spent diagnosing this problem! 17 Responses to "How to resolve "XML Parsing Error at 1:1. Code 4 appears to be expat's XML_ERROR_INVALID_TOKEN per PHP's XML parsing documentation, and the expat.h header file. ribo Topic Author Offline Junior Member Less More Posts: 15 Thank you received: 1 5 years 7 months ago #2 by ribo ok i found the issue www.kunena.org/forum/134-k-15-installati...0-1514-upgrade-issue thanks to the It installed with no error message.

I changed one method signature and broke 25,000 other classes. inkanet Posts: 6Joined: Tue Sep 15, 2009 10:41 pm Top by IToris team » Wed Nov 11, 2009 5:31 pm Inkanet,thank you for this solution. Depalindromize this string! Error 9: Invalid character Time to create page: 0.183 seconds Powered by Kunena Forum © The Kunena Project 2008 - 2016 Joomla is a registered trademark of Open Source Matters, Inc.

From there, go to 'Extensions' -> 'Install/Uninstall'. IToris team Site Admin Posts: 1682Joined: Mon Jan 19, 2009 12:33 pm WebsiteICQYIM Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost Is adding the ‘tbl’ prefix to table names really a problem? Reasonable, perhaps; it looks like expat returns XML_ERROR_INVALID_TOKEN for empty files and invalid UTF-8 code sequences, and an empty file might be the more common occurrence of the two.

And I had a valid templateDetails.xml file in my template's .zip file. this contact form forum.joomla.org/viewtopic.php?f=615&p=2861177 –Elin Dec 8 '12 at 15:53 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote This can happen for a variety of reasons, but all Error 4: Empty document" dating from December 28, 2008 about this problem, so it wasn't just me. I have recently installed SOBI2 and 4RSS components, however when I disable or uninstall them the error still shows up.

Pagination in SQL Server Why does Friedberg say that the role of the determinant is less central than in former times? The method notes the error message, and crosses that file from its list. Error 4: Empty document However, the installation seemed to be successful. have a peek here I already saved a form(not sure if I did correctly)!

Are you using rokweather? At least I know it's not something I'm doing wrong. on 29 Dec 2009 at 03:12 GDR!

Also in the components uninstall window I get XML Parsing Error at 1:1.

known good copies (filesize can be a good indication), and re-upload any corrupted files. Join them; it only takes a minute: Sign up JOOMLA + XML Parsing Error at 1:1496. xillibit Offline Kunena Developer Less More Posts: 9035 Thank you received: 885 5 years 6 months ago #5 by xillibit Yes, Kunena 1.6 works with Joomla 1.5, i advise you to Joomla Hosting by Rochen Ltd.

on 15 Jul 2009 at 00:12 Steve Fuery Thanks Jim, A thorough, technical explanation - most of which was over my head, but I get the idea! The installable archive structure Joomla templates (and other extensions like modules and plugins) are structured as a compressed archive (.zip, .tar.gz, or .tar.bz2 formats all work) containing the various files of The short answer: the error message comes from a metadata file named ._templateDetails.xml, which the Mac OX 10.5.x Finder inserted into the ZIP archive. Check This Out on 18 Apr 2009 at 00:46 Derek Buntin Thanks for the info, i knew it was related to the way our MAC archived the files, but your explanation is awesome.

Please read the blog post for important message. This provokes JSimpleXML to produce the message, XML Parsing Error at 1:1. See Blog: www.kunena.org/blog/178-kunena-5-0-3-released × Before posting new topics in this category K 1.5.x Support: Please read this first. Storage of a material that passes through non-living matter Which movies is this XKCD comic referencing?

Hosting sponsored by: Siteground Terms of Use History Team Privacy Policy Back to top Home| About Joomla| Community| Forum| Extensions| Documentation| Developer| Shop MyGforge Home Home My Stuff Users Search Projects See OSX Considered harmful for someone else who found this behaviour an obstacle. Execute export COPYFILE_DISABLE=true first, then your compress command like zip -r ../mytemplate.zip *. Error 4: not well-formed (invalid token) up vote 0 down vote favorite I am receiving the error: "XML Parsing Error at 1:1496.

on 15 Apr 2009 at 00:06 Leander Hi, I was also getting these XML parsing errors on my OSX machine and I have a simple solution for it. Solutions? There was a Joomla! I selected all the files and directories of the template, right-clicked on one of the file icons, and selected "Compress".

What now?