<?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>RobTucker.co.uk &#187; wordpress</title>
	<atom:link href="http://www.robtucker.co.uk/tag/wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robtucker.co.uk</link>
	<description>Virtual Insanity v2.0 - The Official Website Of Rob Tucker</description>
	<lastBuildDate>Tue, 15 Nov 2011 23:59:16 +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>Warnings Upgrading WordPress Plugins : NearlyFreeSpeech.net</title>
		<link>http://www.robtucker.co.uk/2009/06/11/warnings-upgrading-wordpress-plugins-nearlyfreespeechnet</link>
		<comments>http://www.robtucker.co.uk/2009/06/11/warnings-upgrading-wordpress-plugins-nearlyfreespeechnet#comments</comments>
		<pubDate>Thu, 11 Jun 2009 10:00:35 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[nearlyfreespeech]]></category>
		<category><![CDATA[nfs]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.robtucker.co.uk/?p=370</guid>
		<description><![CDATA[Firstly, I&#8217;ve been using NearlyFreeSpeech for years, and they&#8217;ve always been great. They&#8217;re a very low cost hosting method, working on a pay-as-you-go basis. However, they&#8217;re not the best hosting environment for those that prefer things to &#8216;just work&#8217;. You need to be a little more technically minded to host your site with NFS, or [...]]]></description>
			<content:encoded><![CDATA[<p>Firstly, I&#8217;ve been using NearlyFreeSpeech for years, and they&#8217;ve always been great. They&#8217;re a very low cost hosting method, working on a pay-as-you-go basis. However, they&#8217;re not the best hosting environment for those that prefer things to &#8216;just work&#8217;. You need to be a little more technically minded to host your site with NFS, or at least have some patience.</p>
<p>For the last couple of years, I switched hosting of my main site (this one) to another hosting provider &#8211; BlueHost. However, in the last few months of my time with them, the level of service slipped considerably, to the point where large portions of my site would often disappear or fail to work properly. I switched back to NFS recently, and I&#8217;m so glad I did. Their hosting is quick, reliable, and affordable.</p>
<p>However, as I mentioned, it really is a bare bones solution. There&#8217;s no cpanel here. They wont install WordPress, etc, for you. You need to roll up your sleeves and get geeky in the terminal.</p>
<p>The biggest issue i&#8217;ve faced since moving my site back to NFS, is the inability to upgrade plugins successfully through the dashboard using WordPress 2.7. <span id="more-370"></span>Every time I try to upgrade a plugin, I get a set of warnings along the following lines during reactivation:</p>
<p><span style="font-family: &quot;Courier New&quot;, Courier;">Warning: include_once(/f1/content/xxxxxx/public/wp-content/plugins/all-in-one-seo-pack/) [function.include-once]: failed to open stream: Inappropriate ioctl for device in /f1/content/xxxxxx/public/wp-settings.php on line 473</span><span style="font-family: &quot;Courier New&quot;, Courier;"> </span></p>
<p><span style="font-family: &quot;Courier New&quot;, Courier;">Warning: include_once() [function.include]: Failed opening &#8216;/f1/content/xxxxxx/public/wp-content/plugins/all-in-one-seo-pack/&#8217; for inclusion (include_path=&#8217;.:/nfsn/apps/php5/lib/php/:/nfsn/apps/php/lib/php/&#8217;) in /f1/content/xxxxxx/public/wp-settings.php on line 473</span></p>
<p>It also squirts these warnings into the top of my webpages. Not good! The only way I could work around this warning was to deactivate the plugin, then delete the plugin, and then reinstall the plugin. What a mess.</p>
<p><br class="spacer_" /></p>
<p>Although I&#8217;ve not yet found a fix as such, I have found a decent workaround, which is far easier and quicker than any of the other suggestions I&#8217;ve come across:</p>
<p>1. Deactivate the plugin<br />
 2. Upgrade the plugin<br />
 3. Activate the plugin</p>
<p>Seems simple enough, but this is the only consistent way I&#8217;ve found of upgrading plugins and avoiding the warning messages. If anyone else has any suggestions, please leave me a comment as I&#8217;d be grateful to hear about them.</p>
<p><strong>UPDATE 15/06/2009:</strong> This workaround seems to work very intermittently for me. However, I have noticed a much greater success rate if the &#8216;all in one SEO pack&#8217; is deactivated EVERY time I try to upgrade ANY plugin.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.robtucker.co.uk/2009/06/11/warnings-upgrading-wordpress-plugins-nearlyfreespeechnet/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
