If you’re looking to update your wordpress system, or have done so in the past, then you’re probably familiar with these upgrade steps.

The information given by Wordpress.org is comprehensive and it’s highly advisable to read the extended upgrade process as well, since it mentions important points not given in the three-step update method.

Basically, Wordpress.org explains the most essential points and lists the steps necessary to perform a successful update of the Wordpress system.

Some of the included points are : Checking minimum requirements with your web hosting provider (compatibility of Wordpress with MySQL & PHP versions), how to back up your Wordpress system and a way to avoid custom files such as your theme files from being overwritten by default files during the update process.

As said, the steps are complete, but having upgraded many web CMS systems over the years, I feel there are a few points that can be added.

Read on to see 4 simple, but useful points that I aren’t in the official list, but nonetheless can be important to many Wordpress users who’re planning on updating . . .

1- Waiting a while before updating
Though Beta versions are meant to detect major bugs and annoyances in a new system, it’s still wise to wait a little while before updating after a new version has come out. This waiting period allows you to catch feedback from other users who’ve all ready done the update and are using the new version. After a little while annoyances and problems should already be posted on the Wordpress support forums and by the time you decide to update yourself, many solutions to problems might be available.

B.t.w. it’s surprising how many people end up exploring the support forums only after they run into a problem. The support forums hold a treasure of information about what awaits users in the new version. It’s a good idea to keep exploring the forums during this waiting period.

2- Keeping an eye out for plugin incompatibilities
Checking minimum requirements of the new Wordpress version and checking if they are compatible with the version of your web hosting provider’s technology is one thing, but what about the plugins that you’re using. You may be using relatively old plugins that haven’t been problematic in your current Wordpress version, but may cause some trouble in the updated one.

Did I mention waiting a while before updating ? You’ll probably be able to find posts about plugin problems and the solutions to them them on the forums as well. Chances are also that the plugin author will release an updated version after incompatibilities are discovered. Why would you want be the one to discover the problem ?

3- Choosing a good time to perform the update
During the update process, your Wordpress blog may display disrupted operation. There could be breaks in how the theme is rendered in the browser and functionality is reduced to no more then default, since updating Wordpress requires you to deactivate all plugins during updating.

Taking this into account and if you’re not using the maintenance mode plugin (which allows you to put your blog off line and display a custom message to your audience) it’s wise to choose a time during which you know that traffic levels and promotional activities are at a relatively low point.

Minimizing the effects that maintenance related activities (which includes updating to a new version) have on your audience is one of the priorities that a considerate blogger or web master has.

4- Testing the new version out in a sub folder before updating
A very simple idea, very effective, and basically the most important one in the list. Taking a copy of your current Wordpress blog system, putting it into a sub folder on your domain and upgrading it in this other location provides you with an opportunity to test the new version in the perfect environment. Namely, on your own web hosting account and with the same plugins you’ve been using. Consequently, this is the best way of eliminating chances for unexpected surprises.

I won’t list the steps necessary to install Wordpress in a sub folder in this post, but I take it that anyone who’s planning on doing this knows what they’re doing. For instance, the blog installed in a sub folder should not use the same database as your original blog, but a renamed copy instead. You don’t want your test version to make changes to the database that your original blog is using.

Test-driving the new version is the best way of getting to know the behavior of any new web CMS version. You can perform modifications without worry, check plugin compatibility and see how the whole package behaves on your own web hosting account.

Final words
It’s good to realize that upgrading your wordpress blog can be more than just following a number of given steps leading you through the process. The more serious you take your blog, the smoother and less problematic you want your update process to be, both for yourself as well as your readers.

I’m curious to know which one of the points made above you take into account before updating your Wordpress blog, and if none of the points above, then of course feel free to share your own tips as well . . .