<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: WordPress 2.0.6 released</title>
	<atom:link href="http://www.johntp.com/2007/01/05/wordpress-206-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johntp.com/2007/01/05/wordpress-206-released/</link>
	<description>Blog Tips To Help You Make Money Online</description>
	<lastBuildDate>Thu, 31 Mar 2011 14:24:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: David Bradley</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62861</link>
		<dc:creator>David Bradley</dc:creator>
		<pubDate>Tue, 16 Jan 2007 17:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62861</guid>
		<description>If you&#039;d upgraded from previous version to 2.0.6, you can upgrade (again) to 2.0.7 by uploading and replacing just a half dozen files rather than the whole schebang

http://wordpress.org/download/

these are the replaced files
    * wp-admin/inline-uploading.php
    * wp-admin/post.php
    * wp-includes/classes.php
    * wp-includes/functions.php
    * wp-settings.php
    * wp-includes/version.php

like Wordpress says, it sucks to have another upgrade so soon after the last, and no doubt there will be at least one more before we see ver 2.1. Oh well.</description>
		<content:encoded><![CDATA[<p>If you&#8217;d upgraded from previous version to 2.0.6, you can upgrade (again) to 2.0.7 by uploading and replacing just a half dozen files rather than the whole schebang</p>
<p><a href="http://wordpress.org/download/" rel="nofollow">http://wordpress.org/download/</a></p>
<p>these are the replaced files<br />
    * wp-admin/inline-uploading.php<br />
    * wp-admin/post.php<br />
    * wp-includes/classes.php<br />
    * wp-includes/functions.php<br />
    * wp-settings.php<br />
    * wp-includes/version.php</p>
<p>like WordPress says, it sucks to have another upgrade so soon after the last, and no doubt there will be at least one more before we see ver 2.1. Oh well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress 2.0.7 Released - JohnTP.com</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62820</link>
		<dc:creator>WordPress 2.0.7 Released - JohnTP.com</dc:creator>
		<pubDate>Tue, 16 Jan 2007 11:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62820</guid>
		<description>[...] WordPress 2.0.6 released [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress 2.0.6 released [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62766</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 16 Jan 2007 02:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62766</guid>
		<description>Ah well they just released 2.0.7!</description>
		<content:encoded><![CDATA[<p>Ah well they just released 2.0.7!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62761</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 15 Jan 2007 22:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62761</guid>
		<description>I guess I should upgrade.  Any idea what the security fix is, or do they not want people to exploit the many blogs that are still running old versions?</description>
		<content:encoded><![CDATA[<p>I guess I should upgrade.  Any idea what the security fix is, or do they not want people to exploit the many blogs that are still running old versions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikita</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62590</link>
		<dc:creator>nikita</dc:creator>
		<pubDate>Mon, 15 Jan 2007 06:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62590</guid>
		<description>your download link is very usefull</description>
		<content:encoded><![CDATA[<p>your download link is very usefull</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: manu khanna</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62410</link>
		<dc:creator>manu khanna</dc:creator>
		<pubDate>Thu, 11 Jan 2007 21:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62410</guid>
		<description>I too upgraded to 2.06 butthe one I am eagerly waiting for is 2.1, hopefully being a major release it should have some killer visual enhancements, integrating the WordPress Shuttle &#124; Administration Redesign Project would suffice (almost). If anyone knows of any similar Admin Themes (not WP Tiger Admin Theme), pl. do post back.</description>
		<content:encoded><![CDATA[<p>I too upgraded to 2.06 butthe one I am eagerly waiting for is 2.1, hopefully being a major release it should have some killer visual enhancements, integrating the WordPress Shuttle | Administration Redesign Project would suffice (almost). If anyone knows of any similar Admin Themes (not WP Tiger Admin Theme), pl. do post back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bradley Science Writer</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62044</link>
		<dc:creator>David Bradley Science Writer</dc:creator>
		<pubDate>Sun, 07 Jan 2007 11:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62044</guid>
		<description>Did the upgrade again...working fine now...must have been a failed file overwrite or similar...</description>
		<content:encoded><![CDATA[<p>Did the upgrade again&#8230;working fine now&#8230;must have been a failed file overwrite or similar&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Techmantr</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-62026</link>
		<dc:creator>Techmantr</dc:creator>
		<pubDate>Sun, 07 Jan 2007 08:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-62026</guid>
		<description>Hi Guys i just upgraded my WP version its Gud</description>
		<content:encoded><![CDATA[<p>Hi Guys i just upgraded my WP version its Gud</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bradley Science Writer</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-61946</link>
		<dc:creator>David Bradley Science Writer</dc:creator>
		<pubDate>Sat, 06 Jan 2007 19:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-61946</guid>
		<description>I attempted the upgrade but having backed up mySQL databases etc and replaced all files with the 2.0.6 versions I got an error when running the upgrade script:

Fatal error: Call to undefined function: attribute_escape() in /home/folder/public_html/my-blog/wp-admin/upgrade.php on line 70

This is the offending code:

$goback = attribute_escape(stripslashes(wp_get_referer()));

To get around that I used the upgrade.php file from 2.0.5 which &quot;worked&quot; but Dashboard tells me I&#039;m still running 2.0.5 not 6...despite all-new files.

I&#039;d already done the templates.php patch so maybe needn&#039;t have bothered until things settled down. Anyone else get that error in the upgrade script?

Thanks

db</description>
		<content:encoded><![CDATA[<p>I attempted the upgrade but having backed up mySQL databases etc and replaced all files with the 2.0.6 versions I got an error when running the upgrade script:</p>
<p>Fatal error: Call to undefined function: attribute_escape() in /home/folder/public_html/my-blog/wp-admin/upgrade.php on line 70</p>
<p>This is the offending code:</p>
<p>$goback = attribute_escape(stripslashes(wp_get_referer()));</p>
<p>To get around that I used the upgrade.php file from 2.0.5 which &#8220;worked&#8221; but Dashboard tells me I&#8217;m still running 2.0.5 not 6&#8230;despite all-new files.</p>
<p>I&#8217;d already done the templates.php patch so maybe needn&#8217;t have bothered until things settled down. Anyone else get that error in the upgrade script?</p>
<p>Thanks</p>
<p>db</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rugjeff</title>
		<link>http://www.johntp.com/2007/01/05/wordpress-206-released/comment-page-1/#comment-61932</link>
		<dc:creator>Rugjeff</dc:creator>
		<pubDate>Sat, 06 Jan 2007 16:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.johntp.com/2007/01/05/wordpress-206-released/#comment-61932</guid>
		<description>Thanks for the download link. Been waiting for the upgrade.</description>
		<content:encoded><![CDATA[<p>Thanks for the download link. Been waiting for the upgrade.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

