Must Know Information About
Upgrading to WordPress 3.1!
Every time a major WordPress release arrives, people get scared!
Why? Because just like nearly everything in life… the upgrade procedure can be dangerous.
However, driving cars takes thousands of lives and yet we continue to do it anyways. Why? Because… point #1… when you know the facts and know how to play safe, the risk is minimized.
Why do people get scared? Because we’ve all heard of people losing their blogs to a failed upgrade. Yup. It happens.
However, no blog that is backed up properly is ever really lost and right there is point #2. You must upgrade (more on that in a moment) but you should not upgrade until you have a complete backup. Don’t know how? See this link on how to back up your wordpress blog correctly.
Every single one of my blogs not only ran the early betas but also all the release candidates. (Yes, that means my primary business blog – this one – ran the pre-release!) This has been one of the smoothest version upgrades I’ve seen in a long time. All of the conflicts I’ve run into are plugin related and if you do a proper upgrade procedure… (point #3)… before hitting that upgrade button you will very very likely have zero trouble completing the upgrade successfully.
Yes there are going to be hiccups for a few blogs, it always happens but I and most others in the wordpress support community feel REALLY good about this release’s stability which is (point #4). This release was probably two additional months in the making due to incredibly strenuous attention to details.
WordPress 3.1 is live – meaning you’re going to start seeing a small upgrade notice in your Dashboard… (point #5). It has been through an extended beta test and five (wow) release candidates. It’s just been given the green light! (I’ve been running pre-release versions of it right here on this blog for a couple months now.)
However, even though it is now live, I highly suggest waiting one week (no more, no less) before upgrading (point #6). This gives the masses time to upgrade and find any unspotted flaws. Generally these flaws will be in plugins that were not extensively tested by their developers. By waiting a week and keeping your ear to the ground for a green light from support staff like myself, you ensure the best probability of a trouble-free upgrade.
You can further ensure you will have a smooth upgrade by going to the wordpress plugin repository, searching for any plugins you use, and ensuring they are listed as known compatible with WordPress 3.1. (point #7)
Delaying upgrading your blog more than a few weeks after a major or security update (which this is both) greatly increases your risk of your blog being hacked or infected, which is point #8. Generally speaking the damage done to your business and to your nerves by being hacked and infecting your clients and having to do a long cleanup procedure is far more devastating to your business than a failed upgrade that needs to be recovered from a recent backup. Recoveries aren’t fun but they aren’t so bad either… infection cleanups (particularly including cleaning up your soiled name if you do not realize your infected in time) can be incredibly painful.
If you’re either too uncertain of your ability to upgrade your blog successfully or would rather not be bothered with it, I offer both hourly and contract based support time (point #9). This means I can assist you with your backups, upgrades or both. My clients know that as soon as the green light is given, their blogs will be taken care of by me and my team!
That’s all folks! That’s what you need to know to successfully navigate the arrival of WordPress 3.11! Please share this information as much as possible because while I enjoy doing support work I’d prefer to see crisis cases minimized! What is your biggest concern about WordPress 3.1?
Remember you can always ask here or on my Facebook page (the suggested location) with questions about your specific situation! (point #10)
WordPress.org Blog: WordPress 3.1 Released