<?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>TechPHP.org&#187; WordPress</title>
	<atom:link href="http://www.techphp.org/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techphp.org</link>
	<description>Web development journal</description>
	<lastBuildDate>Tue, 15 Dec 2009 00:04:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Blog HTML Validity and plug-ins</title>
		<link>http://www.techphp.org/general/html/blog-html-validity-and-plugins/</link>
		<comments>http://www.techphp.org/general/html/blog-html-validity-and-plugins/#comments</comments>
		<pubDate>Thu, 18 Dec 2008 01:34:20 +0000</pubDate>
		<dc:creator>simon</dc:creator>
				<category><![CDATA[HTML]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[html validity]]></category>
		<category><![CDATA[page rank]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[syntax highlighter]]></category>
		<category><![CDATA[validator]]></category>
		<category><![CDATA[w3C]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://techphp.net/?p=113</guid>
		<description><![CDATA[Maintaining the Wordpress blog valid to the declared HTML standard seems to be not very easy if many plug-ins are used. In fact, every plug-in contributes a piece of code to the page and sometimes breaks the HTML validity. Since plug-ins can be upgraded by a simple click in the dashboard, an error can be [...]]]></description>
			<content:encoded><![CDATA[<p><img style="margin: 3px 10px; float:left;" title="invalid-xhtml10" src="http://www.techphp.org/wp-content/uploads/2008/12/invalid-xhtml10.png" alt="invalid-xhtml10" width="88" height="31" />Maintaining the <a href="http://techphp.net/wp/" target="_self">Wordpress blog</a> valid to the declared HTML standard seems to be not very easy if many <a href="http://techphp.net/wp/plugins/" target="_self">plug-ins</a> are used. In fact, every plug-in contributes a piece of code to the page and sometimes breaks the HTML validity. Since plug-ins can be upgraded by a simple click in the dashboard, an error can be simply delivered and installed to your Blog. Thus, a re-check in a HML Validator of your choice is desireable after every new plugin upgrade. I prefer to use <a href="http://validator.w3.org/">W3C Validator</a> for checks.</p>
<p>Apparently, I realized running my monthly <a href="http://www.seitwert.de/" target="_blank">seitwert</a>-check, that the one of my pages got errors because of one of the plug-in installed. This time it was <a href="http://wordpress.org/extend/plugins/google-syntax-highlighter">Google Syntax Highlighter for WordPress</a> by <a href="http://www.peterryan.net/">Peter Ryan</a>. Instead of using the <code>type="text/javascript"</code> inside of <code>script</code>-tag, the <code>class="javascript"</code> is used. The bug could be easily fixed locally by replacing the corresponding pieces of code. Peter seems to be not interested anymore in maintaining the plug-in, since there is a long list of comments claiming and voting for the bug.</p>
<p>Especially, if you think of the fact, that the usage of invalid (X)HTML effects your page rank by search engines and other directories in a very negative way, such hidden standards violations should be avoided.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.techphp.org/general/html/blog-html-validity-and-plugins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wordpress 2.7 released</title>
		<link>http://www.techphp.org/general/wordpress-27-released/</link>
		<comments>http://www.techphp.org/general/wordpress-27-released/#comments</comments>
		<pubDate>Fri, 12 Dec 2008 22:18:20 +0000</pubDate>
		<dc:creator>simon</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[2.7]]></category>
		<category><![CDATA[announcement]]></category>
		<category><![CDATA[coltrane]]></category>
		<category><![CDATA[release]]></category>

		<guid isPermaLink="false">http://techphp.net/?p=35</guid>
		<description><![CDATA[Several days ago, the new version of Wordpress &#8220;Coltrane&#8221; has been released. Because this time it is a major release, I spend some time to introduce the new features. Regarding to the Wordpress Blog: &#8220;&#8230;the first thing you’ll notice about 2.7 is its new interface. From the top down, we’ve listened to your feedback and [...]]]></description>
			<content:encoded><![CDATA[<p><img style="margin: 10px; float: left;" title="Wordpress Button" src="http://s.wordpress.org/about/images/buttons/smbutton-blue.png" alt="Wordpress Button" width="58" height="69" />Several days ago, the new version of Wordpress &#8220;Coltrane&#8221; has been released. Because this time it is a major release, I spend some time to introduce the new features. Regarding to the <a href="http://wordpress.org/development/2008/12/coltrane/" target="_blank">Wordpress Blog</a>: &#8220;&#8230;the first thing you’ll notice about 2.7 is its new interface. From the top down, we’ve listened to your feedback and thought deeply about the design and the result is a WordPress that’s just plain faster. Nearly every task you do on your blog will <strong>take fewer clicks and be faster</strong> in 2.7 than it did in a previous version. (<a href="http://wordpress.org/download/">Download it now</a>, or read on for more.)&#8230;&#8221;</p>
<h3>Dashboard</h3>
<p><img style="margin-left: 10px; float: right;" title="wp27dashboard" src="http://www.techphp.org/wp-content/uploads/2008/12/wp27dashboard.png" alt="wp27dashboard" width="154" height="421" />The main improvement of the new version is the complete redesign of the dashboard. The structure of it becomes more convenient and clear (especially in contrast to the old versions like 2.3). The new vertical menu bar on the left is separated in three parts: dashboard anchor, authoring actions and settings. classification eases the usage, especially for the authors and editors.</p>
<h4>Authoring actions</h4>
<p>The authoring actions have a similar classification as in last versions: you will find actions for working with posts, media, links, pages and comments. The corresponding pages has been completely redesigned and use prety much AJAX technology. In the media library, the new items can be uploaded to the library, that allows uploading of items not related to the posts or pages.</p>
<h4>Settings</h4>
<p>The settings control panel was also a subject of reconstruction. The most important features are: support of web installation of plug-ins (finally, no additional file system access to the server is required), automatic wordpress upgrade (making the InstantUpgrade plug-in absolete).</p>
<h3>Upgrade</h3>
<p>The upgrade seems to be running without any problems. As usual by major releases you need to run the DB upgrade using a built-in script. It worked fine for this page.</p>
<h3>Conclusion</h3>
<p>As a conclusion, I recommend the upgrade to the new version. The promise made by the developers in their blog is fulfilled and the blogging systems really operates quicker.  The dashboard redesign seems to be adequate and the features like online-plug-in installation and built-in web update are nice. If you use <a href="http://gears.google.com/" target="_blank">Google Gears</a>, you can enable caching of most static parts and make the blog run very quickly.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.techphp.org/general/wordpress-27-released/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
