<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: WordPress 2.6 is released</title>
	<atom:link href="http://developedtraffic.com/2008/07/15/wordpress-26-is-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://developedtraffic.com/2008/07/15/wordpress-26-is-released/</link>
	<description>Web design, search engine optimization and Internet marketing</description>
	<lastBuildDate>Fri, 20 Apr 2012 18:35:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Diane Vigil</title>
		<link>http://developedtraffic.com/2008/07/15/wordpress-26-is-released/#comment-120718</link>
		<dc:creator>Diane Vigil</dc:creator>
		<pubDate>Tue, 10 Feb 2009 11:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/07/15/wordpress-26-is-released/#comment-120718</guid>
		<description>Hard to say offhand. The first thing I&#039;d check is how you upgraded. This is how I do it:

(1) Back up WP files AND database.

(2) If you normally have problems with plugins, you can disable those in the admin panel before the upgrade.

(3) Delete all WP files on the server EXCEPT for the wp-config.php and themes (and possibly the plugins).

(4) Upload the new WP files and run the upgrade.

If you didn&#039;t delete the old files before uploading the new files, you may find that some of the old files didn&#039;t get overwritten.

Here&#039;s a link to the WordPress forums, searching for &lt;a href=&quot;http://wordpress.org/search/upgrade+2.7+Server+Error?forums=1&quot; target=_blank&quot;&gt;2.7 Server Error&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Hard to say offhand. The first thing I'd check is how you upgraded. This is how I do it:</p>
<p>(1) Back up WP files AND database.</p>
<p>(2) If you normally have problems with plugins, you can disable those in the admin panel before the upgrade.</p>
<p>(3) Delete all WP files on the server EXCEPT for the wp-config.php and themes (and possibly the plugins).</p>
<p>(4) Upload the new WP files and run the upgrade.</p>
<p>If you didn't delete the old files before uploading the new files, you may find that some of the old files didn't get overwritten.</p>
<p>Here's a link to the WordPress forums, searching for <a href="http://wordpress.org/search/upgrade+2.7+Server+Error?forums=1" target=_blank">2.7 Server Error</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keen</title>
		<link>http://developedtraffic.com/2008/07/15/wordpress-26-is-released/#comment-120717</link>
		<dc:creator>Keen</dc:creator>
		<pubDate>Tue, 10 Feb 2009 10:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://developedtraffic.com/2008/07/15/wordpress-26-is-released/#comment-120717</guid>
		<description>I just upgraded to Wp 2.7, But it says Internal server error. I had to roll back to 2.6. Can any one tell me why it gives error in 2.7 ?</description>
		<content:encoded><![CDATA[<p>I just upgraded to Wp 2.7, But it says Internal server error. I had to roll back to 2.6. Can any one tell me why it gives error in 2.7 ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

