Roughly 60 days or so after the release of WordPress 2.3.1, a new release is made available. About 3 days, back, I saw the announcement in the WordPress Admin module.

Here’s what is mentioned in the WordPress Development Blog:

WordPress 2.3.2 is an urgent security release that fixes a bug that can be used to expose your draft posts. 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to […]

I am still rather new to WordPress, and this is like my first attempt at an upgrade. Thus, a visit to the WordPress Upgrade Guide is necessary. After reading through the process required, which is really not that difficult, I decided to first try it out locally on my test environment. Yes, I do have a local test environment running on my notebook. Will certainly put up a post about it. Not now.. Sometime soon.. perhaps..

I went through the upgrade process locally, following all the instructions in the guide. Everything went smoothly. No problems came about after the upgrade. My installed theme and plugins worked fine.

Once I’m satisfied and certain that the upgrade does not break anything in my configuration, I decided to go ahead and upgrade my live blog. Here are the steps which I took to upgrade my live blog to 2.3.2. For the purpose of this posting, let’s assume my current 2.3.1 is installed in a folder named wplive.

  1. Download WordPress 2.3.2
  2. FTP the zip file over to my server
  3. Extract (unzip) the file into a new folder – i.e. wp232
  4. Copy wp-config.php (wplive/wp-config.php) into wp232
  5. Copy additional plugins (wplive/wp-contents/plugins/*.php – exclude the default plugins like akismet and hello) into wp232
  6. Copy additional themes (wplive/wp-contents/themes/* – exclude the default themes like classic and default) into wp232
  7. Copy the upload folder (wplive/wp-content/uploads) into wp232
  8. Rename wplive to wp231
  9. Backup the Database
  10. Rename wp232 to wplive
  11. Run the upgrade module
  12. Configure Permalink
  13. Test the upgrade and ensure there are no errors.

If you read the upgrade guides (short version or extended version), the method of upgrade is slightly different. I like the method above because should the upgrade cause problems, I could easily fall back to the original configuration just by renaming wp231 back to wplive. Of course, a database restore would be required if the db was modified. As it is, the upgrade from 2.3.1 to 2.3.2 doesn’t require any db modifications (I might be wrong, though).

If you’re not into doing the upgrade manually, you could of course upgrade it via Fantastico if your hosting provides it for you. I prefer to do it manually because by doing so, I learn a bit about the system. Besides, it’s really not too hard. What’s so hard about copying files from one folder to another. Just drag and drop.

Have you upgraded your WordPress? Hey, it’s a new year. Why not start the year off with a new version of your blogging tool?