Upgrading to WordPress 2.3 Dexter

September 25th, 2007
Blogging News, WordPress

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.




  1. oyunlar (1 comments.) says:


  2. spencerp (5 comments.) says:

    Just an FYI: Alot of issues currently going on now, can be found in this Support thread.

  3. Jeremy (3 comments.) says:

    I’m not sure why he recommends installing 2.2.3 over the top if you receive the 500 error, as 2.3 deletes the wp_post2cat tables, which is 2.2.3’s form of categorisation. Unless, of course, you receive the 500 errors before you even get a chance to run the upgrade, in which case you should be safe downgrading.

  4. Mark Ghosh (386 comments.) says:

    Good point Jeremy, that will only work if the upgrade did not go through all the way, otherwise the tables will not exist.

  5. Melissa (1 comments.) says:

    …Or just use the automatic upgrade plugin like I did and it’s installed in less than 3 minutes.

  6. Michael (1 comments.) says:

    Regarding svn, i think it’s simpler just using patch/diff files as one doesn’t have to take care about the .svn directories, which i don’t want to delivered by my apache.
    Patch files can easily be generated by the wp trac.


  7. Jenny (24 comments.) says:

    I tried to upgrade and all I got was a blank screen so I give up.

  8. Jeffro2pt0 (164 comments.) says:

    It took me about an hour or two but I was finally able to upgrade my WordPress installation which you can read about here I did experience database errors in relation to the UTW plugin but I ended up fixing those. The tag importer seemed to work flawlessly but I miss the functionality of my UTW plugin already.

  9. Kirk M (67 comments.) says:

    I can state for a fact that running 2.2.3 over a 2.3 upgrade that went all the way through will not work. Backing up your entire 2.2.3 (or whatever version) DB is essential if you need to fall back. I found that I had to drop all 2.3 tables (yes all), import my previous backup’d 2.2.3 DB and then downgrade my WP install to 2.2.3 (keeping the wp-content directory original through out testing of course) and all was well. 2.3 works for me just fine BTW but when I was testing out beta 3 I purposely tried different ways of downgrading and the above is what worked. Others may have been successful using other ways.

  10. Alex (2 comments.) says:

    Spanish version available here

  11. Jeffro2pt0 (164 comments.) says:

    Am I the only one having problems with the INCOMING LINKS section of the dashboard? This thing keeps showing my latests blog posts from the front page instead of showing me links.

  12. Martin (1 comments.) says:

    this is great, im glad virtually all the plugins are working, hopefully wp-email will be soon.

  13. Kelson (20 comments.) says:

    @Jeffro2pt0: It looks like the Incoming Links list switched from Technorati to Google Blog Search. Unfortunately, Google Blog Search doesn’t filter out hits from your own blog, so if you don’t get a lot of incoming links, your own posts will drown out the information you actually want.

  14. Doug Smith (17 comments.) says:

    I just released a plugin called “Upgrade Preflight Check” that may be of help to those upgrading to WordPress 2.3. It scans through your other plugins and themes looking for problems that may cause errors with WordPress 2.3. It’s best to run it before upgrading, but it could also help find plugins or theme elements causing errors after upgrading.

  15. Stephanie Booth (1 comments.) says:

    I’ve been trying to find information on whether upgrade from 2.0.x to 2.3 is possible. Any opinions/experience on that?

  16. Vaibhav Gadodia (8 comments.) says:

    I have just upgraded to 2.3. I was having trouble with an error related to wp_post2cat. Turned out it was an incompatible plugin.

  17. Jeffro2pt0 (164 comments.) says:

    Thanks Kelson, through a friend, I figured out how to change them back to Technorati links.


  1. […] Note: see WTC for details on how to upgrade. […]

  2. […] There are more guides to upgrading your WordPress blog to the latest verstion at the site. […]

  3. […] Another nice post with the same title as mine has some suggestions for people who ran into problems: read it at the Weblog Tools Collection. […]

  4. […] Upgrading to WordPress 2.3 Dexter (Weblog Tools Collection) […]

  5. […] cantidad de gente que hace alharaca sobre la nueva versión de WordPress es increíble: TechTear, Weblog Tools Collection, Blogging Pro, Alt1040 (que inclusive informa sobre la versión en […]

  6. […] and I had none of the issues mentioned in the WordPress Support Forum and in the comments posted at Weblog Tools Collection. I guess it helps that I don’t have that many activated plugins and I tend to keep things […]

  7. […] for example this article on WLTC, where most of the comments mention the fixing of the not existing data tables. This thread at the […]

  8. […] Perhaps I’m getting neurotic about an upgrade that is only here to help. There are plenty of tips on coping with and upgrading to 2.3 and my host does one click upgrades that even saves a copy of the site on the old version in case […]

  9. […] have to say, reading this over at Weblog Tools Collection scared me a […]

  10. […] step failsafe upgrade wordpress 3. WP 2.3 Themes Compatibility 4. WP 2.3 Plugins Compatibility 5. Upgrading WP 6. Preparing for WP […]

  11. […] for example this article on WLTC, where most of the comments mention the fixing of the not existing data tables. This thread at the […]

  12. […] Weblog Tools Collection » Blog Archive » Upgrading to WordPress 2.3 Dexter Op m’n todo-lijstje. (tags: wordpress upgrade) Tags: none […]

  13. To Do’s says:

    […] 8110 top Review McCall M4887 Spay rabbit w of 10/30 Upgrade WordPress when mySQL gets upgraded Upgrading to WordPress 2.3 Dexter WordPress Upgrade Preflight […]

  14. […] for example this article on WLTC, where most of the comments mention the fixing of the not existing data tables. This thread at the […]

Obviously Powered by WordPress. © 2003-2013

page counter