Thread

Hi there

I’m in the process of testing an upgrade from 2.1.3 to 2.2.2 of a fairly large MSM site.

Generally looks to be going well but I have a problem with the login sessions.

The MSM part of the site is actually based on subfolders rather than different domains, so:
“/” is the main site
“/products” is site two and
“/partners” is site three

Previously, logging into the CP or the front end started a user session across all sites. Now, I am only logged into the main site.

Help!

Hi Darren,

It sounds like this is actually the bug in 2.2.1 that was fixed in 2.2.2. Can you double check for me to be sure you’re running on 2.2.2?

EE 2.2.2 - Build: date 20110801
MSM 2.1.0 - Build: 20110630

The bug looks similar, yes, but that report is to do with sites on different domains, these are subfolders of the same domain which perhaps is treated slightly differently?

Well, it’s treated differently, but there are of course some things common to the way sessions are handled regardless of how MSM is set up. At any rate, it’s good to know we’re on the same version while testing.

Could you copy over your cookie settings for all your MSM sites (from each site’s: Admin > Security and Privacy > Cookie Settings).

Also, what kind of Admin Session Type are you using? (here: Admin > Security and Privacy > Security and Sessions)

I’m on a local development domain at present which is http://bcp

For each of the three sites the Cookie domain is set to:
bcp

Path and Prefix are blank

Security settings as per screen grab attached. All three site identical

Was this working previously in the same development environment, the address for which is http://bcp?

The reason I ask is because EE may be expecting the cookies to have an actual, standard format domain name to be present, i.e. http://bcp.dev

Could you give that a try and see if that takes care of it?

Yes, it was working perfectly before.

Changing http://bcp to http://bcp.dev does not help.

Darren,

I’m going to try to replicate this locally to see if it’s a bug in 2.2.2. In the meantime, is there any way you can get this installation to a server where I can get access to it in order to test it out in case I’m unable to replicate it?

any way you can get this installation to a server where I can get access to it in order to test it out

Yes I think that’s the next step. There’s no staging server at present for this site but we do need one so I’ll get that sorted and let you know when it’s ready.

Have sent you a PM with access details for the staging site.

Hi Darren,

Be on the lookout for an email from me. We can’t offer support through PMs, and they’re not a secure way to send login details.

Hi Darren,

It looks like you’ve got quite a bit of customization going on in your config.php file. That’s totally cool, but not something we can help troubleshoot. Since you know your system better than we do, please simplify this config.php file to the standard issue stuff (you can just save this current config.php as config_backup.php).

Once you have a more vanilla config.php, test it out to see if the issue still occurs. If so, let us know and we’ll dig back in.

I don’t know about ‘quite a bit’, just a few lines to support multiple environments.

Anyway, have stripped down config.php and database.php for you

Darren

Thanks for that, Darren. I’m escalating this over to the Dev team to see what’s going on with this. We may have a bug here, I’m not sure.

Thanks for your patience!

Hi. Any news on this please?