Thanks for this your article, it helps me a lot.
I found an option named “wp_1_user_roles” in wp_1_options table. Do I need to chane this option name ?

Regards,
Neoh

PS:
If it can help someone else, here is my SQL queries :

Step 6+7+8, if you are allowed to read information_schema, run this query to get all “RENAME” SQL command :

select concat(‘RENAME TABLE `’, table_name, ‘` TO `’, ‘wp_’, SUBSTRING(table_name, LENGTH(‘wp_1_’)+1), ‘`;’)
from information_schema.tables
where table_schema = ‘wordpressmig’and table_name like ‘wp_1_%’;

Step 9+10, run this query to update keys

UPDATE `wp_usermeta`
SET `meta_key` = concat(‘wp_’, SUBSTRING(`meta_key`, LENGTH(‘wp_1_’)+1))
WHERE `meta_key` LIKE ‘wp_1_%’;

A wise man once said: “Assumptions are the root of all software defects”, and in this case created quite a bit more work for me than is necessary.

I’ve got another MU site that’s about to ship. I’ll try the upgrade again with the proper instructions and see if I can’t get it done in 1/30th of the time it took me the first time.

Thanks for chiming in on the thread, Ron!

The MULTISITE constant is only for switching from WP to a WP Network. It’s not for upgrading MU installs. You didn’t mention the MULTISITE constant but your upgrade process only works if you had added that to your wp-config.

If you don’t add the MULTISITE constant in your wp-config.php, then you can just replace the MU files with the WP 3.0 files & make the htaccess edit that Pete described in his post.

You may be on to something…

I haven’t actually done an upgrade yet, and just installed 3.0 and enabled the multisite so at this point, it’s purely conjecture.