<?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>BuyHTTP Company Blog&#187; wordpress upgrade Archives  &#8211; BuyHTTP Web Hosting Blog</title>
	<atom:link href="http://blog.buyhttp.com/tag/wordpress-upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.buyhttp.com</link>
	<description>Updates from BuyHTTP Internet Services</description>
	<lastBuildDate>Sat, 19 Jun 2010 05:02:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Possible WordPress 2.8 Upgrade Error</title>
		<link>http://blog.buyhttp.com/possible-wordpress-2-8-upgrade-error/</link>
		<comments>http://blog.buyhttp.com/possible-wordpress-2-8-upgrade-error/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 18:27:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[WordPress Tips]]></category>
		<category><![CDATA[wordpress upgrade]]></category>

		<guid isPermaLink="false">http://blog.buyhttp.com/?p=42</guid>
		<description><![CDATA[There is a possible error when using the automated upgrade tool to upgrade to WordPress 2.8. The Problem If you get far enough in the upgrade process that the archive has been downloaded from WordPress and extracted and then hit an error (like bad permissions) WordPress is supposed to delete the new files. Instead it [...]]]></description>
			<content:encoded><![CDATA[<p>There is a possible error when using the automated upgrade tool to upgrade to WordPress 2.8.</p>
<p><strong>The Problem</strong></p>
<p>If you get far enough in the upgrade process that the archive has been downloaded from WordPress and extracted and then hit an error (like bad permissions) WordPress is supposed to delete the new files. Instead it appears that it deletes all the files rendering your blog unusable.</p>
<p><strong>Should BuyHTTP Customers Worry?</strong></p>
<p>Thanks to our fully managed ownership/permissions system you should not run into this issue. Upgrading our blog using the automated tool could not have been easier. If you do run into this issue, thanks to <a href="http://www.buyhttp.com/buyhttp_data_vault.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.buyhttp.com/buyhttp_data_vault.html?referer=');">BuyHTTP Data Vault</a> you can restore all of your files in a matter of a few minutes and be back up and running. Then you can run a manual upgrade.</p>
<p>Follow this bug: <a rel="nofollow" href="http://core.trac.wordpress.org/ticket/10140" target="_blank" onclick="pageTracker._trackPageview('/outgoing/core.trac.wordpress.org/ticket/10140?referer=');">Trac ticket # 10140</a></p>
<p>Found via <a rel="nofollow" href="http://wpengineer.com/caution-when-updating-to-wordpress-2-8/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/wpengineer.com/caution-when-updating-to-wordpress-2-8/?referer=');">WPEngineer</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.buyhttp.com/possible-wordpress-2-8-upgrade-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
