Question

This question already has an answer here:

Duplicate DB sessions created upon Zend_Auth login (1 answer)

Closed 3 years ago.

然而,由于某种原因,我试图将会议储存在一个使用泽斯德会议的数据库中,我的会议已经消失。不能确定是否执行过某些法典,或者是否执行。

我已注意到,会议设计书似乎在经过一段缩略语之后重新印发。

即便在我查阅档案中增加了以下一线:

php_value session.auto_start 0

最终结果是,我每分钟就坐下来一分钟。

这里,我的密码载于我的陷阱档案中。

$config = array(
     name            =>  session ,
     primary         =>  id ,
     modifiedColumn  =>  modified ,
     dataColumn      =>  data ,
     lifetimeColumn  =>  lifetime 
);


$saveHandler = new Zend_Session_SaveHandler_DbTable($config);
Zend_Session::rememberMe($seconds = (60 * 60 * 24 * 30)); 

$saveHandler->setLifetime($seconds)->setOverrideLifetime(true); 

Zend_Session::setSaveHandler($saveHandler);
//start your session!
Zend_Session::start();

除Zentd_Auth在伐木时可能外,我不使用任何其他届会的相关职能。

Infact rememberme 简言之,“会议”职能——最终结果是,我每几分钟都不断gged。

Answer 1

我认为,你可能会出现这一问题,因为你再次要求从本届会议开始纪念“我们的会议”。

您首先必须记住: 既然需要一个会议来安排记住会议的时间,那么我就没有做什么。

rememberMe calls the regenerateId function and the regeneration of the Id is what really needs the session to exist.

Place the rememberMe call after the session start then see how that works for you.

If that isn t it then I don t know what it could be since my code looks similar to yours.

Answer 2

Have you tried something like this?

protected function _initSession() {
    $config = array(
         name   =>  session ,
         primary   =>  id ,
         modifiedColumn  =>  modified ,
         dataColumn  =>  data ,
         lifetimeColumn  =>  lifetime ,
         lifetime  => 60*60*24*30,
    );

    Zend_Session::setSaveHandler(new F_Session_SaveHandler_DbTable($config));        
}

这样一来,在启动数据库会议之后,寿命就定下来,但直接列入初步编制方案——对我来说,我看不出为什么在你的情况下失败了。

Answer 3

I think you need to look once into following values after bootstrap code

session.gc_maxlifetime
session.cookie_lifetime

Answer 4

If You configure session resources in *.ini config file, check resources.session.cookie_domain parameter. I spend 3 hours when I remembered about it.

友情链接