Any pointers on how I can debug this? Should I insert a debug trace and step through the controller and the view? Should I enable logging and insert various log statements?
Thanks. On Monday, October 8, 2012 4:19:59 PM UTC-6, MichaelF wrote: > > I've seen this before but I cannot remember what's causing it. > > I have @auth.requires_login() decorating several of my controller > functions. I log in first, 'go' to one of those controller functions/pages > in my browser, and I get challenged to log in (even though I'm already > logged in). I log in and it takes me where I want to go. On that page I > fill out a form and submit it. That page/controller requires login, and I'm > challenged again, even though the previous page (where I pressed 'submit') > said I was logged in. How did I get logged out? > > On a related note: I take out the 'requires_login' decoration and run. It > seems, though, that the session isn't working. (I know, I know; it's > working, but I'm doing something to prevent it from doing so!) For example, > on the page/controller that creates the form I save a Storage object in > session.meetInfo. When I submit, session.meetInfo isn't there. 'session' is > there but not meetInfo. I have no session.forget() calls anywhere (that I > can see). > > This happens in Chrome and Firefox. I close all Chrome/FF tabs/windows and > start fresh (without restarting); no luck. This is Windows 7, web2py 2.x. > > Thoughts/suggestions? > --
