Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter technomad42

    (@technomad42)

    Resolved. Turns out to be a slight misconfiguration (mine) in MU Domain Mapping that – for some reason – I was getting away with under WP 3.8 but which then broke in the described manner under 3.9.

    >> Turns out to be a slight misconfiguration (mine) in MU Domain Mapping

    Can you let us know what you changed to fix it please?

    +1 Can you post the fix technomad42?

    ditto here on the +1 with help on fix as i’ve been pulling my hair out (well not literally) and have tried all kinds of combinations but to no avail … thus any pointers would be greatly appreciated :>)

    okay i think i’m answering my own +1 as i just now got it all to work for me … e.g., when logged in as super admin, i can now access any of the sites on the network without having to re-log in to sub sites and/or parked domains at sub sites …

    as running start … per original thread by technomad42, i too was having issues with parked domains that were parked and had been set to “Primary” in that they required me to re-login even though i was logged in as Super Admin to mothership network … this was new issue in that pre 3.9 (and/or plugin upgrade) did not have this login issue …

    in summary i had to tweak a couple things – primarily my config file and the plugin settings …

    there is a third thing i did in that i deleted a mu plugin associated with networks-for-wordpress but not sure that is totally related ..??..

    and fourth thing … in that i also changed my htaccess file in that i removed the <IfModule mod_rewrite.c> and </ifModule> that was not part of suggestion for htaccess updates per plugin (see exhibit two) ..??..

    accordingly, thus share details as follows …

    Step One – Changes to config file … in looking at my original config file vs what my latest version of WP 3.9 and MU Domain Mapped 0.5.4.3 showed, i noticed the new suggestion was slightly different from what i had … see below … so i made changes to config …

    Step Two – Select plugin options … i then went back to Domain Mapping Configuration options and checked the following options ->

    – no to -> Remote Login
    – yes to -> Permanent redirect (better for your blogger’s pagerank)
    – yes to -> User domain mapping page
    – yes to -> Redirect administration pages to site’s original domain (remote login disabled if this redirect is disabled)
    – yes to -> Disable primary domain check. Sites will not redirect to one domain name. May cause duplicate content issues.

    Other Steps … not sure the changes to htaccess were important but i did them and that is highlighted in exhibit two …

    the mu file i deleted = networks-mufunctions.php which is part of this plugin -> Networks for WordPress … and while my development site is using this plugin and has networks within networks, my production site was bombing in this sub site log in dept and currently does not have the plugin activated nor other networks hence the deletion just in case it was contributing to problem ..??..

    lastly, the errors i was getting from logging in as super admin to primary site and then trying to access sub sites parked on network had this kind of error and redirection in url bar -> http://mysite.com/wp-login.php?redirect_to=http%3A%2F%2Fmysite.com%2Fwp-admin%2F&reauth=1
    … thus i thought it was cookie issue at first and tried other options including Root Cookie plugin but nada …

    conclusioin = the order in my config file and the settings in plugin were probably the strike zone that got me back on track … the other changes might have helped (or not) but i’m calling it quits and not retesting those hypothesis but share just in case …

    cordially, chuck scott

    ===============================
    Exhibit 01 – old config vs new
    ===============================
    old config had different order of code, had base var defined, and had one line commented out per suggestion of the Networks-for-WordPress plugin …

    new config suggestion was this and i replaced the old with this ->

    define('MULTISITE', true);
    define('SUBDOMAIN_INSTALL', false);
    define('DOMAIN_CURRENT_SITE', 'myprimarysite.com');
    define('PATH_CURRENT_SITE', '/');
    define('SITE_ID_CURRENT_SITE', 1);
    define('BLOG_ID_CURRENT_SITE', 1);

    the previous config was this ->

    define( 'MULTISITE', true );
    define( 'SUBDOMAIN_INSTALL', false );
    $base = '/';
    /**
     * CS Comment out line below per plugins - WP Multi Network and Networks for WordPress
     define( 'DOMAIN_CURRENT_SITE', 'myprimarysite.com' );
     */
    define( 'PATH_CURRENT_SITE', '/' );
    define( 'SITE_ID_CURRENT_SITE', 1 );
    define( 'BLOG_ID_CURRENT_SITE', 1 );

    =========================
    Exhibit 02 – htaccess
    ==========================
    had been this ->

    <IfModule mod_rewrite.c>
    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]
    </IfModule>

    so i changed it to this sans the ifmodule ->

    # 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

    UGH – NEVER MIND on post above as it did not work in reverse … thus my solution = bogus … ugh … yes i can log in as super admin and access sites but if i login at sub site level as super admin and try to access network of sites, no go … have to login again … even worse, when i tweak plugin setttings, i can’t even login to sub site on first try, thus requires double login … imho = something is not right with this plugin at fundamental level with WP 3.9 ..??..

    Thread Starter technomad42

    (@technomad42)

    Before the problem arose, in Network Admin>Sites, I had each domain showing against the relevant site – ie the site Domain was set to the routed domain, e.g. <name>.com. I then had each domain listed in Settings>Domains, with each as a primary. The list included a list of the format:

    <name>.com
    <name>.org

    <subdomain>.<primary domain>.com

    And that was all working fine. Then, at some point during an update, all the routed domains listed in Settings>Domains vanished, leaving only the single <subdomain>.<primary domain>.com entry. The individual sites though were still set correctly to their host domains. I’d also misspelt the remaining sub-domain entry! That’s the point at which I got into that endless authentication loop on everything except the host primary domain. Once I realised that the other domain entries had vanished, just re-entering them (and correcting the sub-domain entry) fixed the problem.

    So, in my case, the problem seems to have been a combination of an update glitch and my failing to check that all settings were preserved.

    HTH

    okay since my previous posts, i now have it working … i reverted back to my original wp-config and htaccess so ignore what i said in those depts … the key changes i had to make to get this to work are as follows:

    1. set the CNAME to the name of the dedicated server, not the primary domain name that hosts the WP Network … previously i had the CNAME set to the primary domain name …

    2. in the plugin options, uncheck option 4 and check option 5 … previously i had option 4 checked and option 5 unchecked …

    enabling or disabling the other options (options 1, 2 and/or 3) seemed to have no effect with my double login issues but options 4 and 5 did …

    thus now i’m back to experience pre upgrades in that as super admin, i can login once to primary site and access all admin panels of sub sites and parked domains sans double log in … and ditto in being able to login at domain parked level sans double logins …

    cordially, chuck scott

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Cookie failure message on login with MU Domain mapped blogs’ is closed to new replies.