Upgrade to WordPress 3.2 having to resort to Manual upgrade mode.

I have just upgraded this blog to WordPress 3.2 and for the first time in a long while I had to revert to the manual method.  While doing the automatic upgrade, I got a Server 500 error (seems to be a common thing with DreamHost) and was left in maintenance mode.

Getting rid of the maintenance mode was easy – just delete the .maintenance file in the root of the blog.  But the failed upgrade left the upgrade in an unstable state – some files were upgraded while other were still at their old versions.

I then just went through a manual upgrade using FTP and now everything seems to be back to normal running WordPress 3.2.

If you spot something out of the ordinary then please drop me a comment so that I can have a look at it.

Happy reading.