.
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:21, "yth" wrote:
>> Dear all,
>> W
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
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. I tried to
use setAuthenticated(false) on users who have already authenticated,
is .htaccess file?
The second line after the RewriteCond is wrong.
It should be more like:
RewriteCond %{HTTP_HOST} ^mydomain\.com$ [NC]
RewriteRule ^(.*) http://www.mydomain.com$1 [QSA,L,R=301]
Bascht
On 15.01.10 14:16, YTH wrote:
Dear all,
Hi, I would like to allow users getting redirecte
Dear all,
Hi, I would like to allow users getting redirected to www.mydomain.com if
they enter mydomain.com in the browser. I added rewrite rule in the
..htaccess that comes with symfony 1.2 but the rewrite rule does not seem to
work. When users enter mydomain.com, their browser continues to u
Dear Campezzia,
I am using Symfony 1.2.9, but the following codes may also work in 1.4.1.
class frontendConfiguration extends sfApplicationConfiguration
{
public function configure()
{
sfValidatorBase::setRequiredMessage("This field is required.");
sfValidatorBase::setInvalidMessage("Th
