The new version of this blog software, WordPress 2.3, is out. And evidently it breaks some plugins. Many of the plugins I use haven’t been updated in years, and aren’t listed on the list of “known broken” or “known working” plugins. One I like a lot is listed as broken, and hasn’t been updated in a while, which makes me think that if I upgrade I’m going to have to do without it. Also, my theme is heavily customized, so I’m not sure if it will work.
So do I wait, or do I upgrade now and accept that lots of things are going to be broken?
5 thoughts on “Should I or Shouldn’t I?”
There’s a plugin (http://smithsrus.com/downloads/wordpress-upgrade-preflight-check/) that checks your other plugins and tries to determine if they’ll be broken by the 2.3 upgrade. I ran it, and it detected some potential problems even in the handful of plugins I use. From the feature list of WordPress 2.3 there doesn’t seem to be any really compelling reason to change yet, so I figure I’ll give it at least a few months and see if things change.
You list many reasons why you shouldn’t upgrade but none why you should. I think that’s pretty clear-cut.
Rone, the biggest reason for upgrading is that WordPress, like so many other PHP applications, is prone to “security hole of the week” syndrome so you have to keep it up to date.
Yeah. I’m wondering about upgrading from 2.2 as well. The question is how long 2.2 remains supported.
WordPress has a low pain-in-the-arse factor if you can cope with the command line (as we all can).
I agree. I’d worry about security holes. Even if 2.3 doesn’t fix any, if they find one, is someone going to patch it in 2.2?
Comments are closed.