Thread

Am I the only OSX 10.6.x user seeing strange behaviour between session control, persistent and session cookies?

Most obviously I get different behaviour between different browsers (Firefox4, Safari5 and Chrome10) and between current logins during the same browser session and separate browser sessions. At the most simple level the (completely non-functional) ‘log in automatically ...’ check-box is erratic across these environments as is EE’s ability to forward the user the to correct ‘site’ control panel.

I am using the current and most up to date versions of EE and running diagnostic on the Guest account (no retention of cookies between user sessions).

I am also experiencing situations where changes to the General Configuration are marked by EE as good (preferences updated) but on screen are not updated. The configuration file server preferences are set to 666. Most obviously this means that across an MSM environment there is only one site url for example whereas in EE1/MSM this was set on a per-‘site’ basis.

So, any thoughts, anyone?

Thanks, Jules

Hi, Jules.

I can’t replicate the problem you’re having with the MSM and the variable {site_url}

I get a different value with each template:

http://test-ee.com/index.php/sample/siteurl
http://test-msm.com/index.php/visitor/siteurl

These are two sites for test-ee.com.

NOTE: This is on EE 2.1.4 beta.

I do have problems with multiple MAMP installs but not with regular ones. What about your experiences?

Sue,

My experience under EE1 and OSX was to never use the Session Control security option as it made life difficult for me. Naturally EE2 uses different security methodologies so requires reappraisal but my only concern is trying to identify why each time my client logs into his EE/MSM installation he ends up at the CP for the “wrong” site.

I understand fully that there’s no explicit correlation between urls (siteone.com) and MSM sites (site_two) so the way EE might route a user to the correct CP could be via a persistent cookie storing that preference.

This can be made to work across multiple logins during the same browser session in both Safari5 and Chrome10 but not in Firefox4 (because Firefox4 cannot logout of EE at all). However as soon as the browser session is renewed all browsers revert back so that Control Panel access starts with the default (site_one) rather than the user’s preference.

This implies that whatever cookies are used to control CP access are non-persistent so that;

1. the “log in automatically” function is rendered useless; and,
2. under MSM the user cannot be redirected to the correct Site Control Panel

Jules

exp_cp_last_site_id is being set when you use masked login, and in some cases it ends up being the wrong site.

I was able to replicate the problem in Firefox with my 2.1.4 beta domains. Let me ask the dev team about this, I saw a few threads about it, but it continues to be a problem.