<?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: How Long Should You Wait to Upgrade WordPress?</title>
	<atom:link href="http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/</link>
	<description>WordPress Themes, Plugins, Hacks, Tutorials, and more!</description>
	<lastBuildDate>Sat, 13 Mar 2010 10:40:18 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chad</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-8452</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Thu, 23 Jul 2009 21:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-8452</guid>
		<description>Yeah. Upgrading can be beyond frustrating. When I upgraded to 2.8, my WP backend got trashed. Only later did I find that my theme wasn&#039;t supported. I was planning on changing it anyway, so I just took that as the catalyst for that change. But then I found every theme I was interested in wouldn&#039;t format properly with the latest version. I did happen to have the latest Options theme and so I decided to use that. But then I found out my feature gallery won&#039;t work with 2.8. Upgrading to 2.8.1 fixed the backend, but front end is still dicey and has some features which won&#039;t work. I feel a little jilted by the author of the theme since it doesn&#039;t support WP&#039;s latest versions and is no longer in production. Also, I think WordPress has an obligation to put a disclaimer on their upgrades, warning people that their site might break if they decide to go with the latest version. I can&#039;t understand why these upgrades aren&#039;t backwards compatible. This reminds me of how Joomla has basically, left its 1.0 users in the dust. 

That said, I think all users should check the internet before upgrading to see if people are having problems with the latest version. Also, I wouldn&#039;t upgrade immediately unless it&#039;s a security vulnerability. Other than that, wait until all bugs are out of the system and, of course, back up like there&#039;s no tomorrow. 

BTW, I&#039;m still a huge fan of both WP and Joomla 1.5. 

Have a great day.</description>
		<content:encoded><![CDATA[<p>Yeah. Upgrading can be beyond frustrating. When I upgraded to 2.8, my WP backend got trashed. Only later did I find that my theme wasn&#8217;t supported. I was planning on changing it anyway, so I just took that as the catalyst for that change. But then I found every theme I was interested in wouldn&#8217;t format properly with the latest version. I did happen to have the latest Options theme and so I decided to use that. But then I found out my feature gallery won&#8217;t work with 2.8. Upgrading to 2.8.1 fixed the backend, but front end is still dicey and has some features which won&#8217;t work. I feel a little jilted by the author of the theme since it doesn&#8217;t support WP&#8217;s latest versions and is no longer in production. Also, I think WordPress has an obligation to put a disclaimer on their upgrades, warning people that their site might break if they decide to go with the latest version. I can&#8217;t understand why these upgrades aren&#8217;t backwards compatible. This reminds me of how Joomla has basically, left its 1.0 users in the dust. </p>
<p>That said, I think all users should check the internet before upgrading to see if people are having problems with the latest version. Also, I wouldn&#8217;t upgrade immediately unless it&#8217;s a security vulnerability. Other than that, wait until all bugs are out of the system and, of course, back up like there&#8217;s no tomorrow. </p>
<p>BTW, I&#8217;m still a huge fan of both WP and Joomla 1.5. </p>
<p>Have a great day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-8152</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 03 Jul 2009 04:30:12 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-8152</guid>
		<description>If you&#039;re working on a serious blog and using it to make money and you don&#039;t have a dedicated dev blog, you&#039;re just asking for trouble.  It&#039;s just too easy to set up a sub domain (beta.mydomain.com) install WP, theme, plugins and test data etc.) and do all your testing there. 

No way would I upgrade my primaries before testing in dev.  That&#039;s just asking for trouble.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re working on a serious blog and using it to make money and you don&#8217;t have a dedicated dev blog, you&#8217;re just asking for trouble.  It&#8217;s just too easy to set up a sub domain (beta.mydomain.com) install WP, theme, plugins and test data etc.) and do all your testing there. </p>
<p>No way would I upgrade my primaries before testing in dev.  That&#8217;s just asking for trouble.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deborah Gray</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7971</link>
		<dc:creator>Deborah Gray</dc:creator>
		<pubDate>Mon, 22 Jun 2009 03:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7971</guid>
		<description>I upgraded 2 of my blogs last week and didn&#039;t run into any problems. I deactivated the plugins and made sure they were compatible with 2.8 before I started.</description>
		<content:encoded><![CDATA[<p>I upgraded 2 of my blogs last week and didn&#8217;t run into any problems. I deactivated the plugins and made sure they were compatible with 2.8 before I started.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theme Playground &#124; Community Roundup: The Pay-for-Plugins Edition</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7940</link>
		<dc:creator>Theme Playground &#124; Community Roundup: The Pay-for-Plugins Edition</dc:creator>
		<pubDate>Fri, 19 Jun 2009 15:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7940</guid>
		<description>[...] When Should You Upgrade? [...]</description>
		<content:encoded><![CDATA[<p>[...] When Should You Upgrade? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elizabeth Richardson</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7924</link>
		<dc:creator>Elizabeth Richardson</dc:creator>
		<pubDate>Thu, 18 Jun 2009 23:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7924</guid>
		<description>I had troubles with a Wordpress UPgrade (as descibed in a post above) but I&#039;ve just built a brand new site using the new Wordpress 2.8 intallation and I think it&#039;s MAGNIFICENT. The admin panel is so much faster and the new functions are extremely useful...thanks to Wordpress and the supportive community of developers for making continued improvements to an already superb platform.</description>
		<content:encoded><![CDATA[<p>I had troubles with a Wordpress UPgrade (as descibed in a post above) but I&#8217;ve just built a brand new site using the new Wordpress 2.8 intallation and I think it&#8217;s MAGNIFICENT. The admin panel is so much faster and the new functions are extremely useful&#8230;thanks to Wordpress and the supportive community of developers for making continued improvements to an already superb platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bcarter</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7923</link>
		<dc:creator>Bcarter</dc:creator>
		<pubDate>Thu, 18 Jun 2009 18:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7923</guid>
		<description>I almost always wait about a month after a new release before upgrading my sites, this gives the plugin authors time to get their acts together and many times the .1 version is out by then.

Most people here know this, but if you don&#039;t make sure you back up your site first, just in case something breaks.</description>
		<content:encoded><![CDATA[<p>I almost always wait about a month after a new release before upgrading my sites, this gives the plugin authors time to get their acts together and many times the .1 version is out by then.</p>
<p>Most people here know this, but if you don&#8217;t make sure you back up your site first, just in case something breaks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Serradinho</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7914</link>
		<dc:creator>George Serradinho</dc:creator>
		<pubDate>Thu, 18 Jun 2009 11:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7914</guid>
		<description>I upgraded and my site is running smoothly, no problems as of yet. I know many people normally wait until the next version is out, like 2.8.1.</description>
		<content:encoded><![CDATA[<p>I upgraded and my site is running smoothly, no problems as of yet. I know many people normally wait until the next version is out, like 2.8.1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliot</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7905</link>
		<dc:creator>Elliot</dc:creator>
		<pubDate>Wed, 17 Jun 2009 17:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7905</guid>
		<description>Wait until 2.8.1. Just to be safe. There&#039;s an important bug issued on trac with the highest priority, where WP unadvertendly would erase some core files during upgrade due to some typos.
http://core.trac.wordpress.org/ticket/10140
The bug has already been fixed but the patching is available from version 2.8.1. If you have your old WordPress 2.7.x go ahead and update. if something goes wrong you can always overwrite it with the old WP. The ticket has the two lines to be changed, you can also open WP 2.8, change the lines and update.</description>
		<content:encoded><![CDATA[<p>Wait until 2.8.1. Just to be safe. There&#8217;s an important bug issued on trac with the highest priority, where WP unadvertendly would erase some core files during upgrade due to some typos.<br />
<a href="http://core.trac.wordpress.org/ticket/10140" rel="nofollow">http://core.trac.wordpress.org/ticket/10140</a><br />
The bug has already been fixed but the patching is available from version 2.8.1. If you have your old WordPress 2.7.x go ahead and update. if something goes wrong you can always overwrite it with the old WP. The ticket has the two lines to be changed, you can also open WP 2.8, change the lines and update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: One Fine Jay</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7899</link>
		<dc:creator>One Fine Jay</dc:creator>
		<pubDate>Wed, 17 Jun 2009 14:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7899</guid>
		<description>Most of the issues that I have encountered when upgrading are over plugins. I personally think that there should be no wait time whatsoever: if the issues are with plugin compatibility, there is enough information for a plugin author to update his work for the core release. That is his responsibility. As someone who manages WP installs for clients, this can be a problem, but I can&#039;t curse the core dev team for that. In most cases my clients rely more on what is offered by the core release than plugins. Everyone&#039;s case is different, though.</description>
		<content:encoded><![CDATA[<p>Most of the issues that I have encountered when upgrading are over plugins. I personally think that there should be no wait time whatsoever: if the issues are with plugin compatibility, there is enough information for a plugin author to update his work for the core release. That is his responsibility. As someone who manages WP installs for clients, this can be a problem, but I can&#8217;t curse the core dev team for that. In most cases my clients rely more on what is offered by the core release than plugins. Everyone&#8217;s case is different, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elizabeth Richardson</title>
		<link>http://wphacks.com/how-long-should-you-wait-to-upgrade-wordpress/#comment-7898</link>
		<dc:creator>Elizabeth Richardson</dc:creator>
		<pubDate>Wed, 17 Jun 2009 14:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://wphacks.com/?p=2105#comment-7898</guid>
		<description>I upgraded my Photography website almost instantly as I&#039;ve never had a problem before...big mistake.
The slideshow and some other features of the next gen gallery plugin wouldn&#039;t work. File permissions changed almost magically too. Took ages going through all files and folders and correcting permissions. That didn&#039;t work.
Tried to revert back to the original version of both the plugin and wordpress, to no avail. Ended up using the backup from my server...thank heaven for backups.</description>
		<content:encoded><![CDATA[<p>I upgraded my Photography website almost instantly as I&#8217;ve never had a problem before&#8230;big mistake.<br />
The slideshow and some other features of the next gen gallery plugin wouldn&#8217;t work. File permissions changed almost magically too. Took ages going through all files and folders and correcting permissions. That didn&#8217;t work.<br />
Tried to revert back to the original version of both the plugin and wordpress, to no avail. Ended up using the backup from my server&#8230;thank heaven for backups.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
