On Jul 9, 9:48 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > You should not ne already logged in after registration. That is not > default behaviour
Although I think it should be - unless you block the registration or require verification. Most websites work like this. I subclass auth in my app to do this, but it's a pain having to keep it synced. Would love to have an option: auth.settings.autologin or auth.settings.login_after_registration F > On Jul 9, 3:11 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > > > From the pov of a novice... > > > The default auth.settings.register_next (user/login) is confusing in > > that after registration you're already logged in, but user/login is > > asking for a login again. f=index might be a better choice. > > > Yes, I know it's easy to override, but the confusion starts with a new > > user playing with the welcome application. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
