If I'm right, you should be able to temporarily get your session started successfully by performing a manual require_once on the file that contains the class that the session is trying to restore.
But that's just a band-aid solution. If that fixes it, then you'll need to modify your bootstrap process to make sure the session is started after the modules have been bootstrapped.
It seems that you are starting your session by using a protected _initSession() method in your bootstrap. I suggest using the built-in session resource instead:
To use it, remove your _initSession() method and add the resources.session config to your application.ini, and make sure it appears *after* the resources.modules section. This will allow your session to be started after the modules have been bootstrapped instead of before.
I hope this helps! :)
--
Hector
--
Hector
On Fri, Jun 11, 2010 at 1:44 PM, greg606 <greg606@gmail.com> wrote:
When is autoloader initialized?
I start the session in the main bootstrap. (I have a modular application)
The problem starts when I try to login (Zend_Auth in user module)
--
View this message in context: http://zend-framework-community.634137.n4.nabble.com/problem-with-session-tp2251761p2252265.html
Sent from the Zend Auth mailing list archive at Nabble.com.
没有评论:
发表评论