<?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>follow the white rabbit &#187; using</title>
	<atom:link href="http://blog.ftwr.co.uk/archives/tag/using/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ftwr.co.uk</link>
	<description>Random commentary...</description>
	<lastBuildDate>Thu, 09 Sep 2010 21:11:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
		<item>
		<title>WordPress 2.0.4 released (Security update)</title>
		<link>http://blog.ftwr.co.uk/archives/2006/07/29/wordpress-204-released-security-update/</link>
		<comments>http://blog.ftwr.co.uk/archives/2006/07/29/wordpress-204-released-security-update/#comments</comments>
		<pubDate>Sat, 29 Jul 2006 09:44:52 +0000</pubDate>
		<dc:creator>westi</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[patch]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[using]]></category>

		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/07/29/wordpress-204-released-security-update/</guid>
		<description><![CDATA[WordPress v2.0.4 has been released with a number of security updates so it is well worth upgrading. To simplfy the upgrade process I decided again to try generating a diff file between 2.0.3 and 2.0.4 and using that to patch my sites rather than uploading a full set of new files. The process for generating [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://wordpress.org/development/2006/07/wordpress-204/" onclick="pageTracker._trackPageview('/outgoing/wordpress.org/development/2006/07/wordpress-204/?referer=');">WordPress v2.0.4 has been released with a number of security updates</a> so it is well worth upgrading.</p>
<p>To simplfy the upgrade process I decided again to try generating a diff file between 2.0.3 and 2.0.4 and using that to patch my sites rather than uploading a full set of new files.  The process for generating the diff file is actually simpler than the one I <a href="http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/">used last time</a>!</p>
<p>Here is the process I took on my local machine to generate the diif file:</p>
<ol>
<li>Generated the patch file with <code>svn diff</code> using the following command (all on one line):<br />
<blockquote><p><code>svn diff http://svn.automattic.com/wordpress/tags/2.0.3 http://svn.automattic.com/wordpress/tags/2.0.4 > ~/2.0.3-to-2.0.4.patch</code></p></blockquote>
</li>
</ol>
<p>I then uploaded the patch file to my server and placed it in my home directory and applied the patch as follows:<br />
<span id="more-158"></span></p>
<ol>
<li>Backed up my WordPress database using the wp-db-backup plugin</li>
<li>Made a copy of my WordPress install files as a backup</li>
<li>Then to apply the patch you change into the root folder of your WordPress blog and enter the following patch command:<br />
<blockquote><p><code>patch -p0 < ~/2.0.3-to-2.0.4.patch<br />
</code></code></p></blockquote>
</li>
</ol>
<p>And it was done! &#8211; There are no database changes between 2.0.3 and 2.0.4 and so upgrade.php does not need to be run as far as I know.</p>
<p>To save you some time if you would like to use this method of upgrade you can download the patch file I generated here: <a href="http://blog.ftwr.co.uk/wp-content/dropbox/2.0.3-to-2.0.4.patch">2.0.3-to-2.0.4.patch</a>.</p>
<p><strong>You use this file with out any guarantee that it will work &#8211; Remember to backup first!</strong></p>
<p><ins datetime="2006-07-31T08:24:22+00:00"><strong>Update:</strong> After reading through <a href="http://markjaquith.wordpress.com/2006/07/30/wordpress-204-upgrade-changed-files-zip-changes-diff-changed-files-list/" onclick="pageTracker._trackPageview('/outgoing/markjaquith.wordpress.com/2006/07/30/wordpress-204-upgrade-changed-files-zip-changes-diff-changed-files-list/?referer=');">Mark Jaquith&#8217;s notes</a> on the upgrade to 2.0.4 from 2.0.3 I&#8217;ve noticed that the above patch file doesn&#8217;t include some new images used in the admin UI (binary files cannot be stored in diff files) to get these new images I suggest you download the zip file that Mark has <a href="http://markjaquith.wordpress.com/2006/07/30/wordpress-204-upgrade-changed-files-zip-changes-diff-changed-files-list/" onclick="pageTracker._trackPageview('/outgoing/markjaquith.wordpress.com/2006/07/30/wordpress-204-upgrade-changed-files-zip-changes-diff-changed-files-list/?referer=');">provided on his blog</a>.</ins></p>
<img src="http://blog.ftwr.co.uk/9538f80a/266bbf65/CCBot/1.0 (+http://www.commoncrawl.org/bot.html).gif" />]]></content:encoded>
			<wfw:commentRss>http://blog.ftwr.co.uk/archives/2006/07/29/wordpress-204-released-security-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 2.0.2 released &#8211; Security update</title>
		<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/</link>
		<comments>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comments</comments>
		<pubDate>Fri, 10 Mar 2006 08:19:07 +0000</pubDate>
		<dc:creator>westi</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[patch]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[using]]></category>

		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/</guid>
		<description><![CDATA[WordPress v2.0.2 has been released with a number of security updates so it is well worth upgrading. To simplfy the upgrade process I decided to try generating a diff file between 2.0.1 and 2.0.2 and using that to patch my sites rather than uploading a full set of new files. Here is the process I [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://wordpress.org/development/2006/03/security-202/" onclick="pageTracker._trackPageview('/outgoing/wordpress.org/development/2006/03/security-202/?referer=');">WordPress v2.0.2 has been released with a number of security updates</a> so it is well worth upgrading.</p>
<p>To simplfy the upgrade process I decided to try generating a diff file between 2.0.1 and 2.0.2 and using that to patch my sites rather than uploading a full set of new files.</p>
<p>Here is the process I took on my local machine to generate the diif file:</p>
<ol>
<li>Exported both 2.0.1 and 2.0.2 from svn using the following commands:<br />
<blockquote><p><code>To get 2.0.2 - svn --force export http://svn.automattic.com/wordpress/branches/2.0<br />
To get 2.0.1 - svn --force export http://svn.automattic.com/wordpress/tags/2.0.1<br />
</code></p></blockquote>
</li>
<li>Generated a patch file using diff:<br />
<blockquote><p><code>diff -U3 -r 2.0.1 2.0 > 2.0.1.to.2.0.2.patch<br />
</code></p></blockquote>
</li>
</ol>
<p>I then uploaded the patch file to my server and placed it in my home directory and applied the patch as follows:<br />
<span id="more-143"></span></p>
<ol>
<li>Backed up my WordPress database using the wp-db-backup plugin</li>
<li>Made a copy of my WordPress install files as a backup</li>
<li>Then to apply the patch you change into the root folder of your WordPress blog and enter the following patch command:<br />
<blockquote><p><code>patch -p1 < ~/2.0.1.to.2.0.2.patch<br />
</code></code></p></blockquote>
</li>
</ol>
<p>And it was done! &#8211; There are no database changes between 2.0.1 and 2.0.2 and so upgrade.php does not need to be run as far as I know.</p>
<p>To save you some time if you would like to use this method of upgrade you can download the patch file I generated here: <a href="http://blog.ftwr.co.uk/wp-content/dropbox/2.0.1.to.2.0.2.patch">2.0.1.to.2.0.2.patch</a>.</p>
<p><strong>You use this file with out any guarantee that it will work &#8211; Remember to backup first!</strong></p>
<img src="http://blog.ftwr.co.uk/9538f80a/266bbf65/CCBot/1.0 (+http://www.commoncrawl.org/bot.html).gif" />]]></content:encoded>
			<wfw:commentRss>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
