<?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>kwatog &#38; co. &#187; upgrade</title>
	<atom:link href="http://kwatog.com/tag/upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://kwatog.com</link>
	<description>tech notes and general nonsense</description>
	<lastBuildDate>Wed, 25 Aug 2010 05:46:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>WordPress Upgrade Error(wp-comments)</title>
		<link>http://kwatog.com/blog/wordpress/wordpress-upgrade-errorwp-comments/</link>
		<comments>http://kwatog.com/blog/wordpress/wordpress-upgrade-errorwp-comments/#comments</comments>
		<pubDate>Sun, 16 Aug 2009 17:07:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[wp-comments]]></category>

		<guid isPermaLink="false">http://kwatog.com/?p=107</guid>
		<description><![CDATA[I&#8217;ve been encountering this for a number of times already and on each time, I had to upgrade WordPress manually(through SSH to make it faster). Now, I was able to partially solve this by removing/renaming the existing upgrade folder under wp-contents. You can follow the steps below. Login to your server via FTP navigate to [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been encountering this for a number of times already and on each time, I had to upgrade WordPress manually(through SSH to make it faster). Now, I was able to partially solve this by removing/renaming the existing upgrade folder under wp-contents. You can follow the steps below.</p>
<ol>
<li>Login to your server via FTP</li>
<li>navigate to <strong>wp-contents</strong> folder</li>
<li>rename the existing <strong>upgrade </strong>folder to a new name(you can also choose to delete)</li>
<li>under wp-contents folder, create a new folder named <strong>upgrade</strong></li>
<li>set permission of the new upgrade folder to 666</li>
<li>re-run the upgrade from within wordpress</li>
</ol>
<p><span id="more-107"></span><br />
The one thing that I noticed in this problem is the fact that it only happens on my WordPress installations on VPS. All other sites sitting on a shared cpanel-powered hosting do not encounter this. So there must be something wrong with my VPS configuration. </p>
<p>I&#8217;ll need to find that out because there&#8217;s still one annoying step that needs to be done before upgrading a WP installation. If you have over a dozen sites to update and they are sitting on different servers, it becomes an issue. A one-click solution would be most welcome.</p>
<p>Do you have any idea how I would be able to solve this?</p>
]]></content:encoded>
			<wfw:commentRss>http://kwatog.com/blog/wordpress/wordpress-upgrade-errorwp-comments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
