I just upgraded to WordPress 2.3. It actually was a bit of a pain in the butt.
I initially attempted to upgrade with:
svn switch http://svn.automattic.com/wordpress/branches/2.3
This resulted in:
Fatal error: Call to undefined function: update_object_term_cache() in /home/theurban/public_html/wp-includes/post.php on line 1772
I attempted to upgrade the database as well as resolve a few conflicts and delete files and check them out again with svn. None of that worked. I eventually decided to switch from using the 2.3 branch to using the 2.3 tag:
svn switch http://svn.automattic.com/wordpress/tags/2.3
This got rid of the PHP error, but now the problem was that I had SQL errors about missing database tables. Apparently, the previous database upgrade failed but apparently still thought it was successful and updated db_version in the wp_options table to the latest version (6124), because trying to upgrade the database again resulted in it claiming that the database was already upgraded. Nice error checking.
I ended up peeking in the database upgrade code in wp-admin/includes/upgrade.php and finding a value that I could manually set db_version to in order to convince the upgrade code to do its thing again:
mysql> select * from wp_options where option_name = 'db_version'; +-----------+---------+-------------+--------------+----------+ | option_id | blog_id | option_name | option_value | autoload | +-----------+---------+-------------+--------------+----------+ | 131 | 0 | db_version | 6124 | yes | +-----------+---------+-------------+--------------+----------+ mysql> update wp_options set option_value = 5538 where
option_name = 'db_version';
This seemed to do the trick and get rid of the SQL errors.
Between this and getting hacked for the second time, I’m again starting to have doubts about WordPress. I just don’t know if there’s any alternative that I’d like better.
FWIW, I switched yesterday, and except for expected plugin breakage (fixed in a few minutes), all was fine.
For what it’s worth, i’ve not upgraded in quite some time.
I run a combination of api_security, a dedicated “nobody” like owner for my web server (that has no write access to my blog’s directory), plus more than a few customized files that kill spammers dead (without even running Askimet.)
I see lots of attempts, but fortunately, no successes.
Frankly, I’ve not seen any really solid reason to upgrade.
I switched to get the new tagging system, and optimised table layouts(performs better, especially under load). The tagging system replaces the category system, while leaving the existing category APIs intact.
Performance seems to be about 100% faster, as measured in two of the heavy server load events on my site. I had one article dugg twice this year, with very similar page views (50-100k/hour, sustained for 6-8 hours). The first event resulted in a server load of 2.4, the second (running 2.3) had a server load of 1.4. Page views between the two were within 10%.
Hi Marc,
Do you run any form of PHP opcode cache e.g. APC, eaccelerator – some of them do not cope very well with having the files changed under them by subversion as they don’t correctly notice the changes.
Hi Marc,
I have the same problem.
Could you, please, explain in details how do you “I ended up peeking in the database upgrade code in wp-admin/includes/upgrade.php and finding a value that I could manually set db_version to in order to convince the upgrade code to do its thing again:” etc
here or by mail ?
Thanks a lot.
Daria.