Upgrade from 2.9.2 to 3.0 rc1. Admin login problem…

I’m assuming you did all this because you’re planning to go from MU to single site? If so … eh. I don’t think that’s the right way to go, or rather, I don’t know if you can go backwards. You’d be better off with a fresh install and an export/import.

If you’re just trying to go WPMU 2.9.2 to MultiSite 3.0, then just upgrade per normal and it works fine.

I guess I need to find out more about MultiSite 3.0. I just thought the codes were the same. 🙁

Mostly sorta. 🙂

Are you trying to:
a) Change a site from MU/Multisite to SingleSite
b) Upgrade 2.9.2MU to 3.0 MultiSite

Since you’re on MU now, I’d stay on that track, personally.

Restore your backup.

Upload the 3.0 files RIGHT over the MU ones. Don’t worry about the database.

Follow the NORMAL upgrade path from there 🙂

Enjoy.

I believe that your DB altering is what goobered the install.

Restore the files and database and ‘start over.’

Also, I don’t know if you CAN easily go from MU/MS to Single, so let’s just first see if we can get you back up and running 🙂

I didn’t add the multiuser line as it states in the WP 3.0 documentation

Didn’t? Do, please 🙂 IIRC it also shows you the Tools -> Network admin section, which is where you’ll find your new .htaccess rules 😉

You added this: define('WP_ALLOW_MULTISITE', true);

The .htaccess rules look something like this:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

Assuming your install is in root.