WordPress.org

1. mpwalsh8
   Member
   Posted 1 year ago #

   I set up multi-site a while ago and created several sub-directory sites for it. It took me a while to get it working but once I did, all was fine.

   I updated to 3.0.4 earlier this week and now need to add one more sub-directory site. Creating the site works fine but I am unable to visit it or login to it. The "Backend" link in the sites dashboard works correctly for the 5 sites I created prior to updating to 3.0.4 but for the one site I created with 3.0.4, I am presented with the login screen. If I go ahead and login, my password is accepted but I am immediately presented with the login screen again.

   I searched the forum for "inability to login" and several threads suggest clearing browser history and cookies. I've tried that and it didn't work and I also tried logging in from a computer that has never visited the web site at all and it didn't work either.

   Any suggestions on how to fix this?

   Thanks,

   Mike

2. Andrea_r
   team pirate
   Posted 1 year ago #

   turn off every single plugin you have to start, just to eliminate a plugin conflict.

   Double check the db tables to make sure they are the same as previously created ones.

3. mpwalsh8
   Member
   Posted 1 year ago #

   I finally had a chance to do this and it didn't make any difference, same behavior. Something has changed between 3.0.1 and 3.0.4. I created all of the other sub-directory sites back on 3.0.1 and they all still behave correctly.

4. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   There were changes from 3.0 to 3.0.1 to cause this but exactly 15 files were changed between 3.0.1 and 3.0.4, and those were mostly XML changes.

   What theme are you using?

5. mpwalsh8
   Member
   Posted 1 year ago #

   WordPress 3.0.1 was released on 7/29/3010 and 3.0.2 was released on 11/30/2010. My primary blog was created on 8/31/2010 along with two sub directory sites. I created three more subdirectory sites on 9/15/2010.

   So the primary site and five subdirectory sites which work were created using 3.0.1. The one subdirectory site which isn't working was created with 3.0.4. The primary site uses the INove 1.4.6 theme, the subdirectory site which isn't working uses 2010 because I've never been able to visit the backend to change it anything else.

6. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   I'm not saying you're wrong, I'm saying the changes in the 15 files didn't really have the ability to do that :)

   Did you remember to disable all your mu-plugins as well?

   Are you sure your .htaccess is correct?

   Have you tried manually re-uploading the 3.0.4 files from a fresh download?

   Has anything changed on your server?

7. mpwalsh8
   Member
   Posted 1 year ago #

   I only have a few plugins and I have them all set for network access so when I turned them off, they were all off for the entire network. I haven't changed the .htaccess file but I went and looked at it and it looks pretty vanilla. Certainly nothing in it which is different than the other subdirectory sites.

   I did reload the WP 3.0.4 release think it might be an issue but it didn't make any difference although it did ask me to upgrade the database again which surprised me a bit.

   To the best of my knowledge, nothing else has really changed other than GoDaddy moved my site from one shared server to another because another customer was swamping the resources on the shared server where I was but I believe I was having this problem prior to the move.

8. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   GoDaddy ... Thems fightin' words.

   Can you share your .htaccess?

9. mpwalsh8
   Member
   Posted 1 year ago #

   Sure can, here it is:
   

   [mpwalsh8@p3nlh026 html]$ more .htaccess
   
   # BEGIN WordPress
   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]
   
   # END WordPress

10. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    This should NOT matter, but is just slightly more optimized... Change
    

    RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]

    to
    

    RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $1 [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $1 [L]

    Back to GoDaddy, though, there have been a LOT of problems with their support of MultiSite. They claim to support SubFolders just fine, but I recall a time, not that long ago, where they cached the .htaccess, so it could take up to an hour for any changes to show up. I'm not pointing fingers, but I would ask them if there are any tweaks they need to make to let your .htaccess be read fully. More than once, I've seen people here in the forums come back with 'GoDaddy made a change and now it works!' Which sucks, cause I wanna know WHAT they're doing so I can tell you!

11. mpwalsh8
    Member
    Posted 1 year ago #

    The change to .htaccess didn't make a difference but I looked at the username associated with the new blog and noticed that the username had no role for the new blog. I created a new blog and made sure the username had admin privileges for the new blog and now it is working. I am going to try it with a couple more blogs to make sure it is working again.

12. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    The change to .htaccess didn't make a difference but I looked at the username associated with the new blog and noticed that the username had no role for the new blog.

    Well ... that would do it. How odd. Was that the user who created the blog?

13. mpwalsh8
    Member
    Posted 1 year ago #

    My primary blog login id.

14. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    I'm assuming you login with the SuperAdmin ID all the time :)

    Were you trying to access it with your SuperAdmin ID or another one? If it was another ID, yeah, you have to add them as admin :)

15. mpwalsh8
    Member
    Posted 1 year ago #

    I had actually tried both with same results - the return to the login screen. I deleted everything and tried and again and then set the new user that was created to be an admin for the created blog and now it is working. Very odd.

16. Marcel
    Member
    Posted 1 year ago #

    I have this very same problem.
    I did a clean install (no plugins) of WP 3.1 RC 3, which was working.
    After converting to a network site (sub-directories) I am redirected to the login page again after logging in.
    Any idea about how I can solve this?

    My .htaccess:

    RewriteEngine On
    RewriteBase /network/
    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).*) $1 [L]
    RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
    RewriteRule . index.php [L]

17. Marcel
    Member
    Posted 1 year ago #

    Exactly the same setup is working in WP 3.04.

    The .htaccess file is slightly different:

    RewriteEngine On
    RewriteBase /network/
    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]

18. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    Log out, dump ALL your cookies, and log back in.

19. Marcel
    Member
    Posted 1 year ago #

    I did and I even used another browser.

20. ronbme
    Member
    Posted 1 year ago #

    M66B and mpwalsh8,

    Just a suggestion but have you tried a local install of WordPress using either MAMP or WAMP?

    This is a great way to rule out all problems with a server. You control everything. You can experiment all you want and once you've got it where you want it, then put it up on your host online server.

    I'm running multi-site locally with 28 web sites. I've put it through the ringer and have been able to resolve all problems. It's much easier to isolate a problem when you don't have to worry about the server setup.

21. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    M66B has another post on this - Continued over here: http://wordpress.org/support/topic/31-rc3-multi-site-sub-folder-login-redirecting-to-login-again?replies=8

    Guys, this is why I kvetch when you make MULTIPLE posts for one issue. It's hell on wheels to sort out where you need support!

    mpwalsh8's issue is resolved, so yay :)

    M66B will be in his other post :)

Topic Closed

This topic has been closed to new replies.