Hi Benjamin,
I’ve seen this before, and I believe it’s due to running your MSM install from subfolders rather than subdomains or separate domains entirely. Technically this wasn’t previously supported, but we were able to figure out the last missing piece to make it all work with another EE user last month. That change to the code will be in the next release of EE. But for now (and ONLY if you are comfortable working directly in EE’s core code), find line 93 of /system/expressionengine/core/EE_Config.php and change this:
// Set the default_ini data, used by the sites feature
$this->default_ini = $this->config;
to this
// Set the default_ini data, used by the sites feature
$this->default_ini = $this->config;
if ( ! defined('REQ') OR REQ != 'CP')
{
$this->default_ini = array_merge($this->default_ini, $assign_to_config);
}
Next, since you are running your MSM Sites as sub-folders of your main domain (as opposed to subdomains or separate domains entirely), you must additionally use a unique $assign_to_config[‘cookie_prefix’] variable in the index.php that sits in each of your Sites’ web roots:
$assign_to_config['cookie_prefix'] = 'example';
$assign_to_config['cookie_prefix'] = 'site2';
...and so on. Since each separate Site has the same base domain name, EE will set the same cookie for each Site without this config variable, effectively causing the browser to overwrite each cookie so only the last Site in the multi_login_sites array will have a valid cookie. (I’ve updated the wiki article you linked above to add this note.)
I also want to check on your method for index.php removal. Based on the above, I’m assuming you’re removing index.php from your URLs. Are you using the officially supported method of removing index.php?
Is everything working as expected now?