It does look that way ... doesn't it!? I expect to run into the same issue with some of the other auth routines. I'm going to put them all into modals and see how well it works. So given the structure of auth, they are all going to need callbacks.
On Mar 23, 10:36 pm, Anthony <[email protected]> wrote: > Congratulations, it appears you are the first person to need a reset > password callback. :-) > > > > > > > > On Friday, March 23, 2012 2:11:13 AM UTC-4, weheh wrote: > > > I'm doing some more of this modal stuff for my login/password routines > > and ran into this problem. Probably an oversight in the code (lots of > > moving parts there!) > > > Traceback (most recent call last): > > File "N:\web2py\gluon\restricted.py", line 204, in restricted > > exec ccode in environment > > File "N:/web2py/applications/myapp/models/0_db_1_user.py", line 171, > > in <module> > > auth.settings.reset_password_onaccept = > > [complete_request_reset_password] > > File "N:\web2py\gluon\storage.py", line 196, in __setattr__ > > raise SyntaxError, 'setting key \'%s\' does not exist' % key > > SyntaxError: setting key 'reset_password_onaccept' does not exist
