It appears WP has gone release candidate. This is a very cool thing.. but, things are not quite ready for release IMHO.
If you use wordpress as standard, the upgrade should, more or less work. If you use cat2tag, ultimate tag warrior or deviate away even just a smidgen from the standard install (and lets face it, an increasingly large base of the wordpress community does) - then expect things to break.. badly.
In my case the upgrade took a horrible toll on the database - the new wp db version is not backwards compatible - if you take the “upgrade” path, perform a backup first or the results will be, well, unpleasant.
Here’s some highlights:
- two critical tables required by 2.0 were not created1 - this broke categories and post count(s)
- inability to post any new entries, or edit existing posts2.
- post content deleted when previewing post, again no data written to the db
- various mySQL errors3.
- incompatible wp db version - once you upgrade, that’s it - recovery time.
This is just scratching the surface. I suspect there are going to be horror stories post upgrade - which is inevitable given just how much ground has been covered to reach 2.0. It’s a massive change with a lot of very new code.
Now, before people go all Russell-Crowe-with-a-mobile-phone on me, I’m not knocking the new version. Far far from it, indeed WP 2.0 is going to kick some serious ass. However, I would not recommend an upgrade. Better to reset as many config options to the ‘default’ vanilla settings first as humanly possible (especially anything that involves “tags”), perform a backup of the core tables that are to be migrated (then back the whole damn thing up, files and all) - start with a 100% clean and empty db.. then import the data carefully, limiting data restore to as few tables as possible (perhaps categories, comments and posts only).
I will be creating a “clone” of this site and importing minimal data into a fresh new install when I feel WP 2.0 is bedded down properly. That, I suspect, is going to be the best method - upgrading anything other than a stock standard install, is not going to work in a large number of cases.. it’s a shame, as that was WP’s strength - one could upgrade virtually anything to Wordpress. With the complexity of code now in-trenched in 2.0, upgrading may no longer be such a strong feature.. time will tell.
- Which required manual table creation in order to gain some form of functionality back (↩)
- Changes did not appear to work - nor were they written to the wp database. (↩)
- WP 2.0 appears to require a very modern mySQL implementation to achieve some tasks- this is going to cause grief for many many people. (↩)
≡ This is a journal entry relating to the topics of code, wordpress.
Brendan Borlase is a Systems and Network Administrator living in Adelaide, Australia, having lived, worked and breathed Information Technology for over 12 years. Learn more.
Feedback is encouraged. If you would like to read more, consider subscribing to the regularly updated RSS Feed.
-
1
Trackback on
Jan 3rd, 2006 at 2:37 pm
Reasons to not upgrade to WordPress 2.0 from 1.5.2
In preperation for doing my first upgrade of an existing WP 1.5 site, I did some research first to try to ensure the process went as smoothly as possible (when I began it which I still havent gotten to yet).
-
2
Pingback on
Mar 8th, 2006 at 5:27 pm
[…] Brendan details problems he encountered in trying to upgrade to WordPress 2.0, (although he now seems to have made some progress in the upgrade, and is actually working on creating a WP 2.0 Theme) summarizing that: […]


Dec 21st, 2005 at 8:54 pm
The latest version of ultimate tag warrior (2.8.9ish) has been tweaked for WP2.0 RC1. Version 2.8.7 and below of the plugin isn’t WP2-friendly (not sure which version you have)
If there are things that are still broken, and you let me know about them; then I can fix them!
Dec 22nd, 2005 at 12:12 am
Indeed. :)
I tested your new WP 2.0 flavour - fully righteous, heh. In my case I think it was the mangled wreak of a db left after the upgrade that broke most functionality. I’ve already notice a couple of fixes posted via SVN which look to sort out some of the sharper edges 2.0 currently has.
Starting with a clean install and migrating data in - given the massive overhaul WP 2 has undergone, is I think going to work more reliably.