SOLVED! I moved the session.connect(...) from the end of my db.py to the top, and now it's ok!
thanks, danny On Wednesday, October 15, 2014 8:29:57 AM UTC+3, [email protected] wrote: > > > I created a new application, changed db.py so that session.connect(…) uses > postgres, > > created a test user, and all seems ok :-( > > so the hunting is still on, what bothers me is that all works ok when > session is stored in file! > > it could be my pam_auth, but it has been working without a problem for a > long time. > > > thanks, > > danny > > On Tuesday, October 14, 2014 4:46:59 PM UTC+3, Anthony wrote: >> >> I cannot reproduce this problem. Could you attach a minimal app the >> reproduces the behavior? >> >> Anthony >> >> On Tuesday, October 14, 2014 9:19:59 AM UTC-4, [email protected] >> wrote: >>> >>> sorry, some correction: >>> >>> the value of auth.user is None, auth is an object. >>> >>> which explains why auth.is_logged_in() is False even after a successful >>> login >>> >>> On Tuesday, October 14, 2014 2:25:20 PM UTC+3, Anthony wrote: >>>> >>>> What exactly is None (i.e., what do you mean that auth is None)? Is >>>> auth defined after connecting the session? >>> >>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
