Check the debug on live with multiple different users logged in and try and
reproduce it.
In your core, just set a _GET var like ( ?t=1 ) to trigger debug:2 so you can
see the query for the session ( you want to note the ID's )
Browse around and make sure it still remains a hash.
There could be some rouge code setting the session id (
$this->Session->id("SOME_STRING_OR_ERROR_EVERYONE_IS_GETTING") )
But, like all tech support, make sure disk space / permissions etc is cool on
the database host machine, and also the web node, make sure server is plugged
in etc.. :-)
On Oct 15, 2012, at 9:29 PM, Jeremy Burns | Class Outfit
<[email protected]> wrote:
> Thanks John. Yup, db sessions. What you say sounds sensible (getting the same
> session id) - just trying to understand why that would happen for some
> organisations and not for others; in other words, it sounds more
> environmental that code. Could it be something to do with cookie settings in
> their environment?
>
> Jeremy Burns
> Class Outfit
>
> http://www.classoutfit.com
>
> On 16 Oct 2012, at 05:25:01, John Hardy <[email protected]> wrote:
>
>> Sounds like people are getting the same session id's
>>
>> Database sessions? If so, debug:2 and check the sql.
>>
>> Php Sessions? check diskspace, server health etc.
>>
>> I had a problem before where I was passing sessions to and from swf files
>> and was setting a session id of "undefined" due to a javascript error and
>> would always get the last person that was logged in.
>>
>>
>>
>> On Oct 15, 2012, at 9:11 PM, Jeremy Burns <[email protected]>
>> wrote:
>>
>>> I have inherited a 1.3 app that has users who belong to organisations. I
>>> have had reports from a few organisations who say that when more than one
>>> user from an organisation is logged in they all see the same user account
>>> (a logged in user from the same organisation). Local and test instances
>>> don't behave like this, and the code pulls up a user record based on
>>> $this->Auth->user('id'), so it sounds as if the session is not functioning
>>> correctly. Anyone experienced this or can give pointers about where to
>>> start looking for the issue?
>>>
>>> --
>>> Like Us on FaceBook https://www.facebook.com/CakePHP
>>> Find us on Twitter http://twitter.com/CakePHP
>>>
>>> ---
>>> You received this message because you are subscribed to the Google Groups
>>> "CakePHP" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected].
>>> Visit this group at http://groups.google.com/group/cake-php?hl=en.
>>>
>>>
>>
>>
>> --
>> Like Us on FaceBook https://www.facebook.com/CakePHP
>> Find us on Twitter http://twitter.com/CakePHP
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "CakePHP" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> Visit this group at http://groups.google.com/group/cake-php?hl=en.
>>
>>
>
>
> --
> Like Us on FaceBook https://www.facebook.com/CakePHP
> Find us on Twitter http://twitter.com/CakePHP
>
> ---
> You received this message because you are subscribed to the Google Groups
> "CakePHP" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> Visit this group at http://groups.google.com/group/cake-php?hl=en.
>
>
--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/cake-php?hl=en.
