WordPress upgraded to 2.3 via Subversion

Leave a reply

This is the only way to upgrade WordPress besides using the latest snapshot:

ayn@NGBERT:~/.../wordpress.svn>svn info
Path: .
URL: http://svn.automattic.com/wordpress/tags/2.2.3
Repository UUID: 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Revision: 6114
Node Kind: directory
Schedule: normal
Last Changed Author: ryan
Last Changed Rev: 6063
Last Changed Date: 2007-09-07 15:21:59 -0500 (Fri, 07 Sep 2007)
 
ayn@NGBERT:~/.../wordpress.svn>svn sw http://svn.automattic.com/wordpress/tags/2.3/
...
Updated to revision 6170.

go to /wp-admin/upgrade.php and perform a database upgrade.

blog at version 2.3.

But of course life is never this easy, when I went into /wp-admin after the upgrade, it kept asking for me to go to /upgrade.php again, I instrumented the code and looked like in /admin/admin.php get_option(‘db_version’) returned 5183 and $wp_db_version was 6124.

In /version.php I see:

$wp_db_version = 6124;

so the app was at the right version, but the db was at 5183 somehow. I went into MySQL and did a “select option_value from wp_options where option_name=’db_version’;” and it returned 6124, so wtf?!

at this point, I realized I was using memcached with my blog, restarted memcached and apache, now it’s all good.

Technorati Tags:

Leave a Reply