Now that WordPress 2.3 Dexter has been released, it is time for everyone to upgrade and check out what the hoopla is all about. Just as in the WordPress 2.3 pre-release coverage, there are a lot of really good resources that discuss preparing your blog for it to be ready for the 2.3 upgrade. Since there is a bigger (relative term, bigger than upgrades in recent memory) chance that many of your plugins and themes might stop working with this new version, checking compatibility and making sure that everything will work as expected is even more important. Here are some resources that might help you make that leap.
- The WordPress Development Blog has a good article on Preparing for 2.3
- Blog Security has an article on 5-step Failsafe upgrade to WordPress
- This is slower but it is much safer (and less service affecting) to create a local copy of your remote WordPress install and use the local copy to check for the problems
- First hand advice from rawiri (I love his theme) on upgrading a live blog to 2.3
I especially love this paragraph, I am going to put it in bold so people notice it and remember it while upgrading a live blog. For people who have installed 2.3 to find that you’re receiving a 500 Internal Server Error or a similar issue that is preventing your site from working, simply install 2.2.3 over the top and you should be up and running again. At least enough to further investigate why 2.3 isn’t working for you.[EDIT] I am not sure this is such a hot idea since if the upgrade went through all the way, 2.2.3 would be missing some tables and things would still be broken.
- Now if you do go back to 2.2.3 and try to re-upgrade at a later time, you might run into trouble with your database, so a backup is very, very important
- [EDIT] WordPress Support thread with 2.3 upgrade database errors and proposed fixes Thanks Spencer
I will keep this post open for editing throughout the day. If you ran into a particular problem upgrading your blog to WordPress 2.3 and think that others could benefit from your experience, please leave a comment or contact me.