<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Read this before upgrading to Wordpress 2.6</title>
	<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26</link>
	<description>Successful Blogging Made Simple</description>
	<pubDate>Fri, 09 Jan 2009 22:44:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Daniel Noll</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15858</link>
		<dc:creator>Daniel Noll</dc:creator>
		<pubDate>Fri, 19 Sep 2008 16:06:16 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15858</guid>
		<description>I'm just now getting around to upgrading to Wordpress 2.6+ from 2.5.1.  I arrived here looking for problems and issues users experienced.

I almost never upgrade immediately on releases (e.g., 2.x) of Wordpress unless it's an immediate bug-fix or security patch release.  I usually wait until the issues have been exposed.  When Wordpress goes to version 3.0, I'll do the same.

Regardless, thanks for providing a forum of sorts for those of us who wait to upgrade.
Cheers,
Dan</description>
		<content:encoded><![CDATA[<p>I&#8217;m just now getting around to upgrading to Wordpress 2.6+ from 2.5.1.  I arrived here looking for problems and issues users experienced.</p>
<p>I almost never upgrade immediately on releases (e.g., 2.x) of Wordpress unless it&#8217;s an immediate bug-fix or security patch release.  I usually wait until the issues have been exposed.  When Wordpress goes to version 3.0, I&#8217;ll do the same.</p>
<p>Regardless, thanks for providing a forum of sorts for those of us who wait to upgrade.<br />
Cheers,<br />
Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Werner Patels - A Dose of Common Sense</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15308</link>
		<dc:creator>Werner Patels - A Dose of Common Sense</dc:creator>
		<pubDate>Wed, 23 Jul 2008 01:45:22 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15308</guid>
		<description>&lt;strong&gt;Scary Wordpress 2.6?...&lt;/strong&gt;

I recently upgraded my Wordpress mirror blog to 2.6. Everything, thankfully, went well. I used an automated upgrade feature provided by my hosting service, which may explain why it worked without any problems. But looking around the Internet today, I c...</description>
		<content:encoded><![CDATA[<p><strong>Scary Wordpress 2.6?&#8230;</strong></p>
<p>I recently upgraded my Wordpress mirror blog to 2.6. Everything, thankfully, went well. I used an automated upgrade feature provided by my hosting service, which may explain why it worked without any problems. But looking around the Internet today, I c&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AP</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15307</link>
		<dc:creator>AP</dc:creator>
		<pubDate>Wed, 23 Jul 2008 01:19:14 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15307</guid>
		<description>I should mention that I also used an automated upgrade provided by my hosting service. Maybe that's the problem. Maybe your problems stem from your manual installation somehow.</description>
		<content:encoded><![CDATA[<p>I should mention that I also used an automated upgrade provided by my hosting service. Maybe that&#8217;s the problem. Maybe your problems stem from your manual installation somehow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AP</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15306</link>
		<dc:creator>AP</dc:creator>
		<pubDate>Wed, 23 Jul 2008 01:17:48 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15306</guid>
		<description>I use the Cutline theme, and the upgrade to 2.6 went off without a hitch. Except for a small coding problem any layperson like myself would be able to fix in seconds (in the widget file) -- with the help of the Wordpress.org knowledge base.</description>
		<content:encoded><![CDATA[<p>I use the Cutline theme, and the upgrade to 2.6 went off without a hitch. Except for a small coding problem any layperson like myself would be able to fix in seconds (in the widget file) &#8212; with the help of the Wordpress.org knowledge base.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: N</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15273</link>
		<dc:creator>N</dc:creator>
		<pubDate>Sat, 19 Jul 2008 23:05:37 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15273</guid>
		<description>I guess I got real lucky. 

However, not one incoming link since I upgraded has registered as a trackback and that makes me nervous. Esp after reading about work they did in the whole "remote access security" stuff, and xmplrc or whatever it is called.</description>
		<content:encoded><![CDATA[<p>I guess I got real lucky. </p>
<p>However, not one incoming link since I upgraded has registered as a trackback and that makes me nervous. Esp after reading about work they did in the whole &#8220;remote access security&#8221; stuff, and xmplrc or whatever it is called.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15267</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Fri, 18 Jul 2008 22:45:06 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15267</guid>
		<description>my upgrade seemed to work just fine...</description>
		<content:encoded><![CDATA[<p>my upgrade seemed to work just fine&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashley Morgan</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15266</link>
		<dc:creator>Ashley Morgan</dc:creator>
		<pubDate>Fri, 18 Jul 2008 22:42:28 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15266</guid>
		<description>I'm pleased that it worked for some of you.  But, the fact that it seems to be causing category destruction seemingly at random is still a major cause for concern.

Martin - Thanks for the link.  As you can see, the solution isn't for the fainthearted.</description>
		<content:encoded><![CDATA[<p>I&#8217;m pleased that it worked for some of you.  But, the fact that it seems to be causing category destruction seemingly at random is still a major cause for concern.</p>
<p>Martin - Thanks for the link.  As you can see, the solution isn&#8217;t for the fainthearted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15264</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 18 Jul 2008 21:59:07 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15264</guid>
		<description>I used the wordpress automatic upgrade plugin.....worked fine..</description>
		<content:encoded><![CDATA[<p>I used the wordpress automatic upgrade plugin&#8230;..worked fine..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tracy</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15263</link>
		<dc:creator>Tracy</dc:creator>
		<pubDate>Fri, 18 Jul 2008 21:12:23 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15263</guid>
		<description>Thanks for the tip, Ashley. I'm glad I went with my gut on this one. I put off upgrading for a couple of days. Yesterday, I was going to attempt it, but couldn't get a proper backup of my site made. So I decided it was a sign and I should just wait. And then I checked out this post today. *phew* Thanks for saving me a lot of heartache.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip, Ashley. I&#8217;m glad I went with my gut on this one. I put off upgrading for a couple of days. Yesterday, I was going to attempt it, but couldn&#8217;t get a proper backup of my site made. So I decided it was a sign and I should just wait. And then I checked out this post today. *phew* Thanks for saving me a lot of heartache.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oslib.com</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15262</link>
		<dc:creator>oslib.com</dc:creator>
		<pubDate>Fri, 18 Jul 2008 20:35:13 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15262</guid>
		<description>thanks for the head up on wp 2.6.</description>
		<content:encoded><![CDATA[<p>thanks for the head up on wp 2.6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Parker</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15260</link>
		<dc:creator>Ian Parker</dc:creator>
		<pubDate>Fri, 18 Jul 2008 18:57:48 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15260</guid>
		<description>Ashley,

I managed to upgrade from 2.5.1 to 2.6 (forgot to deactivate all the plug-ins beforehand, too) with no problems. However, I did encounter some crazy SQL errors today at one point. I ran some repairs on the database and all appears to be well... for now. I would second the suggestion that people stick with 2.5.1 for a bit until the release issues with 2.6 are ironed out, although I decided to stick it out with 2.6. Rolling back is more work than I wish to do at the moment. Also, some plug-ins have been a bit dodgy, but their developers were quick to issue fixes, which is great. In any case, good luck with the eventual upgrade. Be well.


Ian</description>
		<content:encoded><![CDATA[<p>Ashley,</p>
<p>I managed to upgrade from 2.5.1 to 2.6 (forgot to deactivate all the plug-ins beforehand, too) with no problems. However, I did encounter some crazy SQL errors today at one point. I ran some repairs on the database and all appears to be well&#8230; for now. I would second the suggestion that people stick with 2.5.1 for a bit until the release issues with 2.6 are ironed out, although I decided to stick it out with 2.6. Rolling back is more work than I wish to do at the moment. Also, some plug-ins have been a bit dodgy, but their developers were quick to issue fixes, which is great. In any case, good luck with the eventual upgrade. Be well.</p>
<p>Ian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15258</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 18 Jul 2008 15:57:44 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15258</guid>
		<description>That's odd. I've upgraded to 2.6 and all is hunky-dory, even though I have to confess that I didn't take all the precautions.

Next time, I'd better be careful, just in case this happens to me.</description>
		<content:encoded><![CDATA[<p>That&#8217;s odd. I&#8217;ve upgraded to 2.6 and all is hunky-dory, even though I have to confess that I didn&#8217;t take all the precautions.</p>
<p>Next time, I&#8217;d better be careful, just in case this happens to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15257</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Fri, 18 Jul 2008 14:53:33 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15257</guid>
		<description>Cheers for the heads-up Ashley.

I was about to do this, but figure I'll wait a few weeks now. Would prefer if they released security patches in addition to full upgrades.  

A quick googlin' threw up this post on fixing broken cats in 2.6 via the database: &lt;a href="http://blog.cumps.be/wordpress-26-upgrade-fix-missing-categories/" rel="nofollow"&gt;http://blog.cumps.be/wordpress-26-upgrade-fix-missing-categories/&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Cheers for the heads-up Ashley.</p>
<p>I was about to do this, but figure I&#8217;ll wait a few weeks now. Would prefer if they released security patches in addition to full upgrades.  </p>
<p>A quick googlin&#8217; threw up this post on fixing broken cats in 2.6 via the database: <a href="http://blog.cumps.be/wordpress-26-upgrade-fix-missing-categories/" rel="nofollow">http://blog.cumps.be/wordpress-26-upgrade-fix-missing-categories/</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea_R</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15252</link>
		<dc:creator>Andrea_R</dc:creator>
		<pubDate>Fri, 18 Jul 2008 12:14:25 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15252</guid>
		<description>There's no harm in waiting a week or two after a release before upgrading. Usually the last-minute kinks are worked out by then.</description>
		<content:encoded><![CDATA[<p>There&#8217;s no harm in waiting a week or two after a release before upgrading. Usually the last-minute kinks are worked out by then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefano</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15250</link>
		<dc:creator>Stefano</dc:creator>
		<pubDate>Fri, 18 Jul 2008 09:03:27 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15250</guid>
		<description>If only I found your post BEFORE upgrading!! :-(
Now my categories are all messed up...
You say that there is a solution... can you post a link to it please?

Stefano</description>
		<content:encoded><![CDATA[<p>If only I found your post BEFORE upgrading!! :-(<br />
Now my categories are all messed up&#8230;<br />
You say that there is a solution&#8230; can you post a link to it please?</p>
<p>Stefano</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hobson</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15249</link>
		<dc:creator>David Hobson</dc:creator>
		<pubDate>Fri, 18 Jul 2008 05:12:02 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15249</guid>
		<description>I upgraded my blog to 2.6 and it was a flawless upgrade with absolutly no issues what so ever.</description>
		<content:encoded><![CDATA[<p>I upgraded my blog to 2.6 and it was a flawless upgrade with absolutly no issues what so ever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15246</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Fri, 18 Jul 2008 04:32:33 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15246</guid>
		<description>Hi Ashley,

Thanks for the headsup! 

A broken blog kills traffic and SERP. Happened to me in May 2008 when I activated an incompatible plug-in. Took me a month to recover .... am not going to break it again!</description>
		<content:encoded><![CDATA[<p>Hi Ashley,</p>
<p>Thanks for the headsup! </p>
<p>A broken blog kills traffic and SERP. Happened to me in May 2008 when I activated an incompatible plug-in. Took me a month to recover &#8230;. am not going to break it again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: afruit</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15245</link>
		<dc:creator>afruit</dc:creator>
		<pubDate>Fri, 18 Jul 2008 03:50:49 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15245</guid>
		<description>Ha! My laziness may have saved me again!</description>
		<content:encoded><![CDATA[<p>Ha! My laziness may have saved me again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anto</title>
		<link>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15244</link>
		<dc:creator>Anto</dc:creator>
		<pubDate>Fri, 18 Jul 2008 01:51:39 +0000</pubDate>
		<guid>http://www.upstartblogger.com/read-this-before-upgrading-to-wordpress-26#comment-15244</guid>
		<description>Worked fine for me.</description>
		<content:encoded><![CDATA[<p>Worked fine for me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
