<?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>David Currie &#187; WordPress</title>
	<atom:link href="http://david.currie.name/archives/category/technology/web/wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://david.currie.name</link>
	<description>on work and play</description>
	<lastBuildDate>Fri, 03 Feb 2012 23:08:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress upgrade</title>
		<link>http://david.currie.name/archives/2009/01/09/wordpress-upgrade</link>
		<comments>http://david.currie.name/archives/2009/01/09/wordpress-upgrade#comments</comments>
		<pubDate>Fri, 09 Jan 2009 20:23:38 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/?p=761</guid>
		<description><![CDATA[I&#8217;ve finally had a chance to upgrade to WordPress 2.7. It&#8217;s relatively painless since I&#8217;ve switched to updating via Subversion. The only problem I hit was with text widgets. I was seeing an error along the lines of &#8220;Warning: array_keys() [function.array-keys]: The first argument should be an array in wp-includes/widgets.php on line 1044&#8243; which, if [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve finally had a chance to upgrade to WordPress 2.7. It&#8217;s relatively painless since I&#8217;ve switched to <a href="http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion">updating via Subversion</a>. The only problem I hit was with text widgets. I was seeing an error along the lines of &#8220;Warning: array_keys() [function.array-keys]: The first argument should be an array in wp-includes/widgets.php on line 1044&#8243; which, if you Google it, currently appears at the top of a whole host of other people&#8217;s blogs. Deleting all (three) of my text widgets and recreating them seemed to fix the problem. It&#8217;s good to see that threaded comments have finally made it in to the base product. I&#8217;ve previously experimented with a couple of plugins but never turned them live for users as I&#8217;ve never been entirely happy with the way they&#8217;ve been implemented. (As a consequence though you&#8217;ll see that some historical posts already have threaded responses from me.) I have to say that, right now I&#8217;m not a big fan of the revamped admin pages but that may be just lack of familiarity&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2009/01/09/wordpress-upgrade/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenID support</title>
		<link>http://david.currie.name/archives/2008/02/13/openid-support</link>
		<comments>http://david.currie.name/archives/2008/02/13/openid-support#comments</comments>
		<pubDate>Wed, 13 Feb 2008 11:59:50 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2008/02/13/openid-support</guid>
		<description><![CDATA[The observant visitor to this site may already have noticed the addition of OpenID support for logon and commenting on this site. This is easy to achieve with the WP-OpenID plugin. For now I have enabled the option to auto-approve comments submitted with an OpenID. I know having an OpenID doesn&#8217;t necessarily make you a [...]]]></description>
			<content:encoded><![CDATA[<p>The observant visitor to this site may already have noticed the addition of OpenID support for logon and commenting on this site. This is easy to achieve with the <a href="http://wordpress.org/extend/plugins/openid/">WP-OpenID</a> plugin. For now I have enabled the option to auto-approve comments submitted with an OpenID. I know having an OpenID doesn&#8217;t necessarily make you a good person but, at least for now, its more effort than your average spammer is prepared to go to.<br />
<span id="more-468"></span><br />
Whilst I was at it, I added the <a href="http://wordpress.org/extend/plugins/yadis/">WP-Yadis</a> plugin so that I could delegate from the URL for this site to an OpenID server. My original intention was to set up my own server using <a href="http://siege.org/projects/phpMyID/">phpMyID</a> but in the end I decided that I preferred the richer functionality provided by my existing <a href="https://www.myopenid.com/">myOpenID</a> account (in particular, the ability to log in with a client certificate) and I&#8217;m not sufficiently paranoid to worry about them knowing what sites I use. In fact, here are the sites that I&#8217;ve been able to use my new identity with over the past couple of days: <a href="http://www.blogger.com/">Blogger</a>, <a href="http://www.dopplr.com/">DOPPLR</a>, <a href="http://www.plaxo.com/">Plaxo</a>, <a href="http://www.technorati.com/">Technorati</a> and, of course, <a href="http://david.currie.name/">this site</a>.</p>
<p>As part of playing around with phpMyID, I also finally got round to <a href="http://articles.slicehost.com/2007/12/3/ubuntu-gutsy-installing-nginx-from-source">recompiling nginx</a> with SSL support. As reported <a href="http://sudhanshuraheja.com/2007/09/remove-nginx-from-ubuntu-fiesty-fawn.html">elsewhere</a>, the only issue I encountered was with removing the default nginx installation.</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2008/02/13/openid-support/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Upgrade weekend</title>
		<link>http://david.currie.name/archives/2008/01/13/upgrade-weekend</link>
		<comments>http://david.currie.name/archives/2008/01/13/upgrade-weekend#comments</comments>
		<pubDate>Sun, 13 Jan 2008 21:54:41 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Hosting]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2008/01/13/upgrade-weekend</guid>
		<description><![CDATA[Finally had a chance to put in place a whole upgrades on this site. First up was WordPress 2.3.2. I then needed to upgrade Gallery2 for the latest version of the WPG2 so that&#8217;s now at 2.2.3. The WPG2 plugin now acts a lot more like I&#8217;d expect a plugin should. Two minor niggles. Firstly, [...]]]></description>
			<content:encoded><![CDATA[<p>Finally had a chance to put in place a whole upgrades on this site. First up was WordPress 2.3.2. I then needed to upgrade Gallery2 for the latest version of the <a href="http://wordpress.org/extend/plugins/wpg2/">WPG2</a> so that&#8217;s now at 2.2.3. The WPG2 plugin now acts a lot more like I&#8217;d expect a plugin should. Two minor niggles. Firstly, it adds its own page which appears with all the others on the right. You can rename it but I&#8217;d rather like to get rid of it completely! Secondly, it doesn&#8217;t work with Gallery URL rewrites. Need to investigate that further but it is mitigated to a certain extent by enabling Lightbox support so you won&#8217;t usually get to the image page from a blog post anyway.<br />
<span id="more-454"></span><br />
Next up was an Ubuntu upgrade to Gutsy Gibbon. The first two times my SSH connection dropped leaving the system hosed. Fortunately I&#8217;ve paid for <a href="http://www.slicehost.com/">slicehost</a> backups so I could simply restore the server. Typically, the third time when I ran the upgrade under a screen session, the connection stayed up!</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2008/01/13/upgrade-weekend/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changing servers</title>
		<link>http://david.currie.name/archives/2007/07/13/changing-servers</link>
		<comments>http://david.currie.name/archives/2007/07/13/changing-servers#comments</comments>
		<pubDate>Fri, 13 Jul 2007 17:29:12 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[Hosting]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2007/07/13/changing-servers/</guid>
		<description><![CDATA[So, it&#8217;s been a little bit quiet on this blog for the past few days. The main reason is that it&#8217;s been on the move from the hosting provided by our ISP (PlusNet) to my SliceHost slice. Things would have been much quicker had I not decided to switch Apache for the increasingly popular (due [...]]]></description>
			<content:encoded><![CDATA[<p>So, it&#8217;s been a little bit quiet on this blog for the past few days. The main reason is that it&#8217;s been on the move from the hosting provided by our ISP (<a href="http://www.plus.net/">PlusNet</a>) to my <a href="http://www.slicehost.com/">SliceHost</a> slice. Things would have been much quicker had I not decided to switch <a href="http://httpd.apache.org/">Apache</a> for the increasingly popular (due to its low memory usage) <a href="http://nginx.net/">nginx</a>.<br />
<span id="more-392"></span><br />
As is the beauty of a virtual server, with the click of a mouse I had a clean Dapper Drake install to start with. Rather than install nginx from source, I decided to <a href="http://wiki.slicehost.com/doku.php?id=upgrade_ubuntu_dapper_-_edgy_-_feisty">upgrade to Feisty Fawn</a> and install via apt. This means losing the long term support of Dapper but, hey, its my server and I&#8217;ll just have to upgrade again when necessary. From there, getting an nginx, mysql, Rails and PHP setup is <a href="http://www.urbanpuddle.com/articles/2007/05/09/install-ruby-on-rails-on-ubuntu-feisty-fawn">well documented</a>, on top of which I added an <a href="http://blog.codefront.net/2007/06/11/nginx-php-and-a-php-fastcgi-daemon-init-script/">init script for FastCGI</a>.</p>
<p>Then things started to get a little tricky. Our blogs use clean URLs for both <a href="http://www.wordpress.net/">WordPress</a> and <a href="http://gallery.menalto.com/">Gallery2</a> but these generate rewrite rules for Apache&#8217;s mod_rewrite. Translating these to nginx for WordPress is fairly <a href="http://www.romej.com/archives/515/nginx-rewrite-rules-for-wordpress-redux">straightforward</a> but, despite many wasted hours, I&#8217;ve failed to get Gallery working correctly. The problem appears to be that nginx URL encodes when rewriting from the path to parameters and Gallery doesn&#8217;t seem to handle this well. Anyway, in the end I&#8217;ve gone ahead with the move but with Gallery rewrites turned off.</p>
<p>I&#8217;ve also switched to using SliceHost&#8217;s nameservers for one of the domains. The other is still stuck with PlusNet as the nameserver as the registrar (<a href="http://www.123-reg.co.uk/">123-reg</a>) returns an error when I try and update the settings.</p>
<p>If you can see this post then all of the important bits are working though!</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2007/07/13/changing-servers/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress 2.2</title>
		<link>http://david.currie.name/archives/2007/05/20/wordpress-22</link>
		<comments>http://david.currie.name/archives/2007/05/20/wordpress-22#comments</comments>
		<pubDate>Sun, 20 May 2007 21:01:48 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2007/05/20/wordpress-22/</guid>
		<description><![CDATA[Having missed the previous security update I decided to upgrade to WordPress 2.2. I&#8217;m glad to say everything seems to have gone smoothly (although PlusNet managed to take the site down again at one point which had me a little worried). Nothing really different for you, the reader, to see. Widget support is now there [...]]]></description>
			<content:encoded><![CDATA[<p>Having missed the previous security update I decided to upgrade to <a href="http://wordpress.org/development/2007/05/wordpress-22/">WordPress 2.2</a>. I&#8217;m glad to say everything seems to have gone smoothly (although PlusNet managed to take the site down again at one point which had me a little worried). Nothing really different for you, the reader, to see. Widget support is now there out of the box but then I had the plugin installed previously anyway.</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2007/05/20/wordpress-22/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome back blogroll</title>
		<link>http://david.currie.name/archives/2007/03/16/welcome-back-blogroll</link>
		<comments>http://david.currie.name/archives/2007/03/16/welcome-back-blogroll#comments</comments>
		<pubDate>Fri, 16 Mar 2007 22:59:49 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2007/03/16/welcome-back-blogroll/</guid>
		<description><![CDATA[Apologies to those whose sites have recently been absent from the links in my sidebar. The modifications in WordPress 2.1 to use the same categories for posts and links managed to break my pages. Having just moved up to WordPress 2.1.2 this is now fixed so the blogroll returns.]]></description>
			<content:encoded><![CDATA[<p>Apologies to those whose sites have recently been absent from the links in my sidebar. The modifications in WordPress 2.1 to use the same categories for posts and links managed to break my pages. Having just moved up to WordPress 2.1.2 this is now fixed so the blogroll returns.</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2007/03/16/welcome-back-blogroll/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Another WordPress upgrade complete</title>
		<link>http://david.currie.name/archives/2007/01/26/another-wordpress-upgrade-complete</link>
		<comments>http://david.currie.name/archives/2007/01/26/another-wordpress-upgrade-complete#comments</comments>
		<pubDate>Fri, 26 Jan 2007 20:56:24 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2007/01/26/another-wordpress-upgrade-complete/</guid>
		<description><![CDATA[I&#8217;ve now moved this blog and Christine&#8217;s up to WordPress 2.1. I&#8217;m still waiting for the WPG2 patch which resolves an issue with g2image and TinyMCE but as I rarely post via the web then this isn&#8217;t too much of a problem. More problematic was that WordPress now appears to add an extra paragraph tag [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve now moved this blog and <a href="http://www.curries.org.uk/christine">Christine&#8217;s</a> up to <a href="http://www.wordpress.org/">WordPress</a> 2.1. I&#8217;m still waiting for the <a href="http://wpg2.galleryembedded.com/index.php/Main_Page">WPG2</a> patch which resolves an issue with g2image and TinyMCE but as I rarely post via the web then this isn&#8217;t too much of a problem. More problematic was that WordPress now appears to add an extra paragraph tag in around the images which broke the style applied to the <a href="http://gallery.menalto.com/">Gallery</a> <em>one-image</em> class. Having moved that to the <em>ImageFrame_none</em> class everything appears to be functioning again.</p>
<p>One slightly annoying side-effect of the fact that categories are now shared between links and posts, when combined with my earlier <a href="http://david.currie.name/archives/2007/01/16/wordpress-upgrade-and-widget-fix/">fix</a>, is that the empty <em>Blogroll</em> category now appears in my sidebar. Maybe one day I&#8217;ll implement the fix properly and hide entries that don&#8217;t have any posts in themselves or their sub-categories! In the meantime I just have to sit back and enjoy the new <a href="http://wordpress.org/development/2007/01/ella-21/">2.1 features</a>.</p>
<p><b>Update 28/01/07:</b> Looks like wp_list_cats has now been fixed so that the hierarchical view does show empty categories with posts in sub-categories (indeed, the post count includes these) so I can remove my earlier fix.</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2007/01/26/another-wordpress-upgrade-complete/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress upgrade and widget fix</title>
		<link>http://david.currie.name/archives/2007/01/16/wordpress-upgrade-and-widget-fix</link>
		<comments>http://david.currie.name/archives/2007/01/16/wordpress-upgrade-and-widget-fix#comments</comments>
		<pubDate>Tue, 16 Jan 2007 22:36:51 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2007/01/16/wordpress-upgrade-and-widget-fix/</guid>
		<description><![CDATA[I&#8217;m glad I didn&#8217;t get round to moving up to WordPress 2.0.6 as, 10 days later, 2.0.7 is out. The upgrade itself went pretty smoothly. I&#8217;ve also fixed the categories widget in my sidebar. By default it doesn&#8217;t show categories without any postings but, in a hierarchical view, it doesn&#8217;t take in to account that [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m glad I didn&#8217;t get round to moving up to WordPress 2.0.6 as, 10 days later, 2.0.7 is out. The upgrade itself went pretty smoothly. I&#8217;ve also fixed the categories widget in my sidebar. By default it doesn&#8217;t show categories without any postings but, in a hierarchical view, it doesn&#8217;t take in to account that sub-categories may have postings. Having selected <em>Sidebar Widgets</em> in the plugin editor, I located the <em>widget_categories</em> function in question. In the call to <em>wp_list_cats</em> I added <em>&amp;hide_empty=0</em> to the end of the parameter. You should now be able to see my <em>People</em> category (empty) but also its <em>Family</em> and <em>Friends</em> sub-categories (with postings).</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2007/01/16/wordpress-upgrade-and-widget-fix/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Upgrade to WordPress 2.0.5</title>
		<link>http://david.currie.name/archives/2006/11/21/upgrade-to-wordpress-205</link>
		<comments>http://david.currie.name/archives/2006/11/21/upgrade-to-wordpress-205#comments</comments>
		<pubDate>Tue, 21 Nov 2006 22:59:42 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2006/11/22/upgrade-to-wordpress-205/</guid>
		<description><![CDATA[Finally found the time to upgrade to WordPress 2.0.5. The process of copying across all the modified files, plugins, themes etc. is always far more manual than I&#8217;d like so if you spot anything that looks broken please let me know!]]></description>
			<content:encoded><![CDATA[<p>Finally found the time to upgrade to WordPress 2.0.5. The process of copying across all the modified files, plugins, themes etc. is always far more manual than I&#8217;d like so if you spot anything that looks broken please let me know!</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2006/11/21/upgrade-to-wordpress-205/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Upgrade time</title>
		<link>http://david.currie.name/archives/2006/09/09/upgrade-time</link>
		<comments>http://david.currie.name/archives/2006/09/09/upgrade-time#comments</comments>
		<pubDate>Sat, 09 Sep 2006 20:50:00 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2006/09/09/upgrade-time/</guid>
		<description><![CDATA[Though it was about time I upgraded the various technologies running this blog. After a few heartstopping moments where nothing worked, I&#8217;m now successfully running Gallery 2.1 and WordPress 2.0.4 with WPG2 2.0 tying the two together along with the newest WordPress Gallery theme. There&#8217;s probably not much to see for the viewer but WPG2 [...]]]></description>
			<content:encoded><![CDATA[<p>Though it was about time I upgraded the various technologies running this blog. After a few heartstopping moments where nothing worked, I&#8217;m now successfully running <a href="http://gallery.menalto.com/">Gallery</a> 2.1 and <a href="http://wordpress.org/">WordPress</a> 2.0.4 with <a href="http://wpg2.galleryembedded.com/index.php/Main_Page">WPG2</a> 2.0 tying the two together along with the newest <a href="http://www.galleryembedded.com/forums/viewtopic.php?t=2636">WordPress Gallery theme</a>. There&#8217;s probably not much to see for the viewer but WPG2 was certainly easier to setup this time and the TinyMCE plugin now lets you add wpg2id tags which is bonus.</p>
<p>I&#8217;ve also added the remote module to Gallery so that I can now used <a href="http://gallery.menalto.com/wiki/Gallery_Remote">Gallery Remote</a> to ease the process of uploading photos.</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2006/09/09/upgrade-time/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Widgets, links and spam</title>
		<link>http://david.currie.name/archives/2006/06/21/widgets-links-and-spam</link>
		<comments>http://david.currie.name/archives/2006/06/21/widgets-links-and-spam#comments</comments>
		<pubDate>Wed, 21 Jun 2006 20:55:10 +0000</pubDate>
		<dc:creator>Dave</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://david.currie.name/archives/2006/06/05/widgets-links-and-spam/</guid>
		<description><![CDATA[If there is anyone that actually visits this site then they have noticed that the right-hand column has changed a bit recently. This is as I&#8217;ve added WordPress Widgets to my template. The presence of a del.icio.us widget has encouraged me to sign up for an account there to store my links. I should probably [...]]]></description>
			<content:encoded><![CDATA[<p>If there is anyone that actually visits this site then they have noticed that the right-hand column has changed a bit recently. This is as I&#8217;ve added <a href="http://automattic.com/code/widgets/">WordPress Widgets</a> to my template. The presence of a <a href="http://del.icio.us/">del.icio.us</a> widget has encouraged me to sign up for an account there to store <a href="http://del.icio.us/dcurrie">my links</a>. I should probably also mention another <a href="http://automattic.com/">Automattic</a> project &#8211; <a href="http://akismet.com/">Akismet</a> &#8211; without which this site would have rapidly disappeared under the weight of spam comments. This saved me from the dilemma of whether or not to add <a href="http://en.wikipedia.org/wiki/Captcha">captcha</a> support to the blog with the associated <a href="http://www.w3.org/TR/turingtest/">accessibility issues</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://david.currie.name/archives/2006/06/21/widgets-links-and-spam/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

