Support » Networking WordPress » Can't login to new Network Site

Viewing 15 replies - 1 through 15 (of 20 total)
  • Andrea Rennick

    (@andrea_r)

    Customer Care at Copyblogger Media and Studiopress

    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.

    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.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    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?

    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.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    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?

    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.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    GoDaddy … Thems fightin’ words.

    Can you share your .htaccess?

    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

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    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!

    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.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    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?

    My primary blog login id.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    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 🙂

    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.

    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]
Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Can't login to new Network Site’ is closed to new replies.