Last updated October 4th, 2013 at 10:28 am
Should you update to the newest version of WordPress?
Probably not right away.
WordPress 3.5 (representing a major release, succeeding Version 3.4.2) was released to the public a little over a week ago. And it offers some exceptional new goodies. But I still say: hold off on updating.
When you logged into your WordPress dashboard, you were probably greeted with:
WordPress 3.5 is available! Please update now.
Should you have updated? Should you update now if you haven’t yet?
Like I said, probably not right away.
Why not?
Because first versions of software usually have bugs.
Because your Web site might depend on the proper functioning of some plugin that worked fine pre-update but crashes post-update.
So, unless you’re prepared to revert your WordPress Web site to its previous state in the event of an update-related crisis, I’d hold off.
Don’t they test these things?
Yes, many people tested the software in its “beta” version. But way many more will test it in its release version. Let them identify bugs and shortcomings. (They’ve already started.)
Many WordPress developers I know have updated only one or two test sites to 3.5, leaving their production sites (and their clients’ production sites) on version 3.4.2. These are people who create WordPress plugins and WordPress custom themes for a living. They develop WordPress Web sites. They write books and tutorials about WordPress.
One-Click Automatic Update is tempting, but…
These are people who didn’t simply click the “automatic update” button. Instead, they followed a painstaking procedure involving multiple backups.
For the more belt-and-suspenders types among us, here’s a procedure borrowed from colleague MaAnna Stephenson:
- complete backup of the WordPress database and files
- update plugins and themes
- check your site
- complete backup again
- update WordPress
- check your site
- complete backup again
- update plugins and themes again
- check your site
- complete backup again
Did you employ the above — or some other responsible — procedure (such as the one recommended in the WordPress.org codex) prior to updating? Are you prepared to?
How about me?
At this writing, I have updated only one WordPress Web site to 3.5: this one. I’m looking for plugin problems and have already found (and reported) some. I’m monitoring many WordPress-related discussion forums where I hear about others’ issues with WordPress 3.5. I’ll keep you posted.
In the meantime, a word to the wise…
Like what you see? Share with others and join my mailing list. No long-term commitment, unsubscribe any time.
Good thing I am slow to check the plugin update stuff. I look forward to hearing from you when it is o.k.
And my guess is that will probably be shortly after 3.5.1 is released.
🙂
Couldn’t agree more. The announcement of a new version tells me to put a follow-up item on my calendar for 90 days from now to see how the release is going.
Considering the source (COO of a software development company), I’m honored by the endorsement!