Upgrade from 2.9.2 to 3.0 rc1. Admin login problem... (46 posts)

  1. Jim R
    Posted 5 years ago #

    Ok...moving from WPMU 2.9.2 to WP 3.0 is NOT fun. :)

    I did all the proper backing up of files and data, so nothing is lost forever. I deactivated all my plugins, and I deleted all the old files except for wp_config and a couple of others. I have a previous test site of WP 3.0, so I used that wp_config.

    I changed all my wp_1_*datatable names* to just wp_*datatable names*. I ran the upgrade database program as I tried to access my Dashboard, and my site is back up, minus plugin functionality.

    The problem is I can't login to my Dashboard now. I get this:

    You do not have sufficient permissions to access this page.

    I tried resetting the password, nothing is working.

  2. Jim R
    Posted 5 years ago #

    It looks like the issue is the Usermeta table. Is there a way to convert WPMU users to WP users?

  3. 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.

  4. Jim R
    Posted 5 years ago #

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


  5. 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

  6. Jim R
    Posted 5 years ago #

    I didn't care, that's likely the most correct answer, but I would eventually want a multisite, especially now since it's all tied together...mostly sorta. :)

    As I look at MultiSite information, there doesn't seem to be much there on how 'upgrade per normal'. I did what I did above then uploaded a regular wp-config file. That hasn't worked, and it seems to revolve mostly around the Usermeta.

    What should I do?

  7. 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 :)


  8. Jim R
    Posted 5 years ago #

    I should restore both, the WPMU files and the database? I altered the database thinking I might use more single site. Or should I just install the 3.0 files and link up to the database?

  9. 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 :)

  10. Jim R
    Posted 5 years ago #

    Back up and running. All I did was restore the database. Let me ask before getting to what's below, I didn't add the multiuser line as it states in the WP 3.0 documentation. I suppose I'm good to go on that note. It appears to be working. It says Super Admin.

    Secondary, likely more important is I'm getting this notice now:

    The wp-content/blogs.php file is deprecated. Please remove it and update your server rewrite rules to use wp-includes/ms-files.php  instead.

    I know how to delete the file, just not sure where I need to rewrite what it says.

  11. 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 ;)

  12. Jim R
    Posted 5 years ago #

    I did, but I don't get the Tools -> Network option.

  13. 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.

  14. Jim R
    Posted 5 years ago #

    Yes, I added toward the end. Should I put that in my .htaccess file?

  15. Jim R
    Posted 5 years ago #

    I did put that in my .htaccess file and uploaded, but nothing has changed. Yes, this is all in my root.

  16. Yes, I added toward the end.

    Where? Seriously, it matters. I put mine JUST below the section for Authentication Unique Keys and Salts.

  17. Jim R
    Posted 5 years ago #

    I put it right below define( "WP_USE_MULTIPLE_DB", false );

    I moved it below the unique keys, still not showing.

  18. *peers* Huh, I don't have it on my MU->3.0 upgrade either.

    Well. Put in the htaccess stuff I have you, and that'll take care of the rewrite rules it mentioned. If the rest is working then yay! And I'll poke around and see if this needs a trac or if I'm just being extra thick headed!

  19. Doogman
    Posted 5 years ago #

    Thank you all for your diligent and passionate work! As a long-time WordPress user I fully appreciate the effort being expended here and wish to convey my gratitude to you all. CHEERS! Eager to see the final release, I'm sure it will ROCK!!

  20. @Ipstenu -0 if they upgrade from MU, they don't need the network rewrites rules. not all of 'em anyway, as they have most of them already.

    I'll be documenting the one they do need. It's just an edit of an exciting one.

    Just a note for thsoe playing the home game: If you are on MU, DO NOT follow the instructions for enabling a network - you already have one!

  21. if they upgrade from MU, they don't need the network rewrites rules. not all of 'em anyway, as they have most of them already.

    Right, which occurred to me later on. That said, WHY doesn't the network menu show up? :) In my back brain, it's should.

    I did an upgrade of MU to MS by just overlaying the 3.0 files and running the upgrade. Seemed to work just fine.

  22. Jim R
    Posted 5 years ago #

    The network menu never showed up for me. I just took out the multisite code and the code suggested for htaccess. Still no network menu. I have the Super Admin menu.

  23. The code I gave you for the .htaccess specifically addresses this line from your earlier post:

    ... update your server rewrite rules to use wp-includes/ms-files.php instead.

    Without it, your uploads will wander off and get lost.

    I guess you don't need the Network menu, but it's still weird to me that you don't. How else do you know what the htaccess should be?

  24. Jim R
    Posted 5 years ago #

    I don't even know what it should mean, so I'm good. :)

    I deleted the blog.php file, and the message went away. I made sure the ms-files.php was present. All 'seems' to be OK other than not having the Network menu you're referring to. What I have seen are network options in other places, like in activating themes and plugins. I don't mean just in the Super Admin part, but contextually within my Dashboard.

    What I eventually want, if I'm going to get use out of multisite, is for Users to 'subscribe' via one site and access to others as a result.

  25. The network menu just shows you how to set your blog up, so it's not like you're missing out on anything huge. To the point that ... I didn't even notice I didn't have it on my MU->MS site until recently :)

  26. epschmidt
    Posted 5 years ago #

    I went through the upgrade from MU 2.9.2 to 3.0 Multisite as directed and it went ok. I am also missing the Network link in Tools and I am having some Admin link problems. In the Super Admin -> Sites area, when I try to move between site backends, the URL's are not updating. They stay relative to whatever site backend I happen to be in. So for example, if i'm in at site1/wp-admin and I try any of the links for site2, they still lead to site1/wp-admin. I've checked my .htaccess and it seems to be right. Any ideas?

  27. What happens if you go to site2/wp-admin?

  28. epschmidt
    Posted 5 years ago #

    It's the same, whatever site I am in the backend of the admin links only lead to that site. Another example, when I am in the My Sites area, where there are links to Visit and Dashboard for each of my sites, the visit links lead to the correct URL's, but the Dashboard links, all lead to the admin area of whatever site's backend I am in.

  29. I think I'm confused.

    When you go into the backend, the links are SUPPOSED to be for that site. Each site has it's own 'stand alone' admin side.

    The only part that cross-links would be the SuperAdmin parts, of which I think they all 'act local' until you switch blogs, either by going to Super Admin > Sites or manually going to site2/wp-admin

  30. epschmidt
    Posted 5 years ago #

    All the menu links are working as expected, Appearance, Tools, etc. It's the links between the sites' admin areas that aren't functioning correctly.

    If I am in Super Admin -> Sites, the link to each of my sites "Backend" leads to whatever site I am currently in. So I have 5 sites, if I'm in the backend of domain.com, the "Backend" link for each of my additional sites leads to domain.com/wp-admin, instead of domain.com/site1/wp-admin, domain.com/site2/wp-admin and so on.

    I can manually change what site I am editing by typing in the correct URL, but that will eventually become a pain as we add more sites.

Topic Closed

This topic has been closed to new replies.

About this Topic