As many of you probably know and are aware of, WordPress 3.2 was released on July 4, 2011.
I am not usually one to jump right into upgrading especially when there is a major release or version upgrade involved in anything. I decided to wait a few days to see what others were saying about the upgrade.
After reading a few posts from people that had upgraded, most of it seemed fairly positive with successful results.
So then I started thinking about the plugins I have installed and whether they would work after upgrading or not. I researched the more popular ones I use over at http://wordpress.org/extend/plugins/ and most claimed they would work. A few of them said not enough data yet.
Since I was fairly confident that the upgrade would be easy enough and the majority of the plugins I use would be compatible I decided to go for it.
The process used to upgrade to WordPress 3.2
1. Verify and Check Hosting Requirements
PHP 5.2.4 or greater (old requirement – since WordPress 2.5 was PHP 4.3 or greater)
MySQL 5.0.15 or greater (old requirement – since WordPress 2.9 was MySQL 4.1.2 or greater)
2. Backup Database and Files
There are a number of plugins and services out there that you can use for this. I personally prefer to use my hosting control panel to download both my database and files.
Whichever method you use be sure to do this. You will kick yourself for not having a backup of your database and files should something go wrong. Don’t count on your host having a current backup. They could be a week old.
3. Export Your Site
–>Download Export All Content
If you have a custom template / theme you may see reference to it. Selecting the all option should include your template related, but you may want to download it separately just to make sure.
4. Deactivate All Plugins
You may not need to deactivate or disable all your active plugins, but in the event that any of them are not compatible or up-to-date to work with the new WordPress 3.2 they may cause the upgrade to fail and/or lock you out of your admin panel.
You can check or tick the bottom “Plugin”, then in the “Bulk Actions” drop down choose “Deactivate” to hit them all at once.
If you have a lot of plugins be sure you deactivate them all. You may have more than 1 page of them to deactivate.
5. Automatic Upgrade
Return to your Dashboard and find the Please update now link and click on the Update Automatically button.
If all is well you should be automatically upgraded to WordPress 3.2.
6. Reactivate All Plugins
You can then go and reactivate all your plugins.
You might clear your cache if you are using some form of caching plugin.
Check your plugins settings to make sure they look right, and you are good to go.
The WordPress 3.2 Dashboard
Another WordPress site I upgraded after clicking on the update automatically link it downloaded and did some auto updating. But, it informed me that my database also needed upgrading, and all I had to do was simply click a button to do so. It did its thing and everything was good to go. So this particular site there was another step involved. Afterwards, reactivating plugins and clearing the cache.
Overall it was a very fast and simple process in my opinion with no problems.
I have read a few posts where people said the upgrade failed for them, and they had to do some manual uploading and tweaking. This is why a database and file backup are necessary just in case something goes wrong or unexpected.
Additionally I would make sure you set a side enough time to perform the upgrade and allow additional time in case there is a problem. You probably don’t want to start an upgrade right before you need to leave for work.
Luckily all my plugins seem to be compatible and working properly after upgrading. I will keep an eye on them for a while just to make sure, but so far everything looks good.