> > Is this solution feasible? But I don't know how to do steps 6-7.
>
> > - Original Message -
> > From: "ken"
> > To: "symfony users"
> > Sent: Thursday, January 28, 2010 11:15 PM
> > Subject: [symfony-users] Re: Mak
ill that old session
> 8. A session attribute member_id is set to his member id in the new session
>
> Is this solution feasible? But I don't know how to do steps 6-7.
>
>
>
> - Original Message -
> From: "ken"
> To: "symfony users"
ssage -
> From: "ken"
> To: "symfony users"
> Sent: Thursday, January 28, 2010 11:15 PM
> Subject: [symfony-users] Re: Making sure a login id only has one session at
>
> any moment
>
> The best solution for this is use database session. Add session_id
&
M
Subject: [symfony-users] Re: Making sure a login id only has one session at
any moment
The best solution for this is use database session. Add session_id
column in the Profile table. This field has to be set during login. So
if you are using sfGuardUserPlugin, you can override the signIn m
uot;
Sent: Thursday, January 28, 2010 9:57 PM
Subject: [symfony-users] Re: Making sure a login id only has one session at
any moment
Why do you want to kill his old session?
On 28 led, 04:21, "yth" wrote:
Dear all,
When a user logins, the controller calls the following function in
isAuthenticated and setAuthenticated sets only LOCAL Cookies. So if he
logins from another computer this functions doesn't check this, but if
ANOTHER User is logged in at the SAME computer, so you can delete his
e.g. credentials first before adding the new ones...
On 28 Jan., 04:21, "yth" wrote:
The best solution for this is use database session. Add session_id
column in the Profile table. This field has to be set during login. So
if you are using sfGuardUserPlugin, you can override the signIn method
in myUser. With the session_id at hand you will be able to check if
user is signed in in a
I think you can set a field in database setting login status to true.
Now if the person again logs in and you find from database, you can
take him to the logout screen/error screen.
On Thu, Jan 28, 2010 at 7:27 PM, Tom Ptacnik wrote:
> Why do you want to kill his old session?
>
>
> On 28 led, 04:
Why do you want to kill his old session?
On 28 led, 04:21, "yth" wrote:
> Dear all,
>
> When a user logins, the controller calls the following function in the
> myUser.class. The problem is, if he doesn't logout but then logins in
> another computer/browser, the old session does not get killed.
