<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>/dev/GON.cl &#187; joomla</title>
	<atom:link href="http://blog.gon.cl/en/cat/development/php/joomla/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.gon.cl</link>
	<description>blog respaldo anti-amnesia</description>
	<lastBuildDate>Thu, 05 Aug 2010 15:54:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Respect you yourself should (Joomla Critique #1)</title>
		<link>http://blog.gon.cl/en/post/676</link>
		<comments>http://blog.gon.cl/en/post/676#comments</comments>
		<pubDate>Wed, 11 Mar 2009 06:29:27 +0000</pubDate>
		<dc:creator>gon</dc:creator>
				<category><![CDATA[joomla]]></category>
		<category><![CDATA[cms]]></category>
		<category><![CDATA[crítica]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://blog.gon.cl/?p=676</guid>
		<description><![CDATA[While working to re-build a site formerly used joomla 1.0, I had a little trouble in the control panel of the new 1.5, because I was leaving an error message.
Fortunately it was not fatal, since it could also modify the site parameters without much inconvenience. But it is not comfortable to see that something is [...]]]></description>
			<content:encoded><![CDATA[<p>While working to re-build a site formerly used joomla 1.0, I had a little trouble in the control panel of the new 1.5, because I was leaving an error message.</p>
<p>Fortunately it was not fatal, since it could also modify the site parameters without much inconvenience. But it is not comfortable to see that something is not right, except for a large system such as Joomla. </p>
<p>The error indicated that I had an XML file that was not being parsed properly, but it&#8217;s not saying which file or which was wrong.</p>
<p>Then I downloaded a backup of the site, and replicate it on my local machine to find out the error. I remembered that there are thousands of Linux applications for console enough powerful to <strong>parse</strong> and <strong>validate</strong> the XML&#8217;s from my site.</p>
<p>I had <a href="http://blog.gon.cl/post/12">an enjoyable experience with the <strong>find</strong> command</a>. But I was missing the command to validate an xml file. Searching the web, I found that possibly the command <strong>xmllint</strong> I could. But ultimately did not help, this reveals a small unexpected detail.</p>
<p><strong>xmllint</strong> has an option to validate, but to do this work, requires that 1) the XML file using a defined DTD or 2) it passes a DTD as a parameter. Testing without using a DTD by parameter, I tried the following:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">find. <span style="color: #660033;">-name</span> <span style="color: #ff0000;">&quot;*.xml&quot;</span> <span style="color: #660033;">-exec</span> xmllint <span style="color: #660033;">--noout</span> <span style="color: #660033;">--valid</span> <span style="color: #ff0000;">&quot;{}&quot;</span> \;</pre></div></div>

<p>Unfortunately, the result was not what I expected. ALL XML files except one, were invalid because they didn&#8217;t have defined the DTD. Thanks to that file that it was, I found that joomla has on its site a DTD file so that developers include it in yours XML configuration files. In this way, the developer requires that your XML files have the structure that the system requires.</p>
<p>The worst&#8230; that single valid file, was a third-party plugin and not the official developers. That is, the official joomla developers do not respect their own rules when writing code.</p>
<p>Finally, xmllint was not what I was looking for, and only had to check the file was malformed (bad labels closed nested bad &#8230;). As I did not know, see on a mailing list (the one I have in the list of <a href="http://blog.gon.cl/foss">FOSS Communities</a>), where I got the solution: <strong>xmlwf</strong>.</p>
<p>Just change the above command with the following matter and fixed:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">find. <span style="color: #660033;">-name</span> <span style="color: #ff0000;">&quot;*.xml&quot;</span><span style="color: #660033;">-exec</span> xmlwf <span style="color: #ff0000;">&quot;{}&quot;</span> \;</pre></div></div>

<p>I found the causers (they were 2), which I fixed and gave the matter ended.<br />
But I stayed with the bitter taste of the disregard that the Joomla developers as a mere detail. What gives me confidence for when a new system update?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.gon.cl/en/post/676/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.389 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-09-09 05:17:40 -->
