Upgrading to WP 2.0

Thanx Podz

I have a question about the definition of ‘Multi-user blogs’

Do you mean like mu.*

or do you mean like changing: $table_prefix = ‘wp_’ to ‘something_’

I posted this question at
http://new.wordpress.org/support/topic/53212

thanks for your pre-emptive assistance! 🙂

thanks again podz…

but to be clear, (i dont want to mess this one up) lets say I have ten multiple ‘blogs_’ running now – and want to try 2.0 on ‘blog03_’ – do I have to back up ALL the others at the same time, or can I just do ‘blog03_’

thanks again for your patience 🙂

Each database and core set of files should be backed up before any upgrade is done. If they are each independently running their own DB, then only #3 needs backing up, but remember, as it’s a current mantra, you can never have enough backups.

Great work with the release and the website guys, I set up a tester at http://yse-uk.com/wp2/, working great.

Working like a charm on my site! 🙂

“1. BACKUP EVERYTHING, I know it’s been said but just incase 🙂
2. Delete all files and folders where your old WP install was – EXCLUDING wp-config.php and the wp-content directory.”

There’s an easier and ‘safer’ way — again backup everything, (obviously, it’s just plain foolishness to do this without a full backup), then rename the original top level wordpress directory (or move it into a new directory). This leaves everything intact (the db included, read on for that), a simple rename & 5 seconds later the ‘old’ blog is back – no “risky” recovery needed.

Download and extract the new WP 2.0 version. If one has access to phpmyadmin then life is easy – backup the existing database (try and minimize taking the ‘cruft’, plugin tables and the like can be recreated as needed by the plugins.. the idea is to give the upgrade process the best chance of success) – open it in a text file and do a ‘search and replace’ for the prefix (e.g. wp_) and replace with something like new_. Create a new db, import the modified sql back in, update the wp-config.php with the new prefix and then perform the wp-admin/upgrade.php process.

This all has some nifty advantages:

1) the original files remain intact – reversal takes 10 seconds to rename the new and old directories
2) the original db (and any additional tables) is still available without a restore (very handy)
3) the new db can be worked on without impacting the existing blog db (a restore is only as good as the last backup made). 😉
4) one can run concurrent (old + new) blogs to keep a web presence if “diving in the deep end” is a scary thought.

With this process one is not deleting or modifying any part of the original blog – it’s all intact and 5 seconds of renaming will bring it back. Having the old and new blogs on the go is also useful if one is going to do a more ‘full on’ layout change.

Yep, WordPress 2.0 is not backwards compatible database and file wise, hence the version step.

I reactivated my plugins and now for where the author name should be it gives me this:

WordPress database error: [Unknown column ‘user_level’ in ‘where clause’]
SELECT COUNT(*) FROM wp_users WHERE user_level > 1