> > Yes I have that already.
Note, your code shows auth.settings.login_after_registration = False. > I'm starting to think that the problem is with my controller, not with the > db.py settings. Maybe my controller is not actually registering the users? > Here's the controller for the signup: > > def signup(): > if auth.is_logged_in(): > redirect <http://127.0.0.1:8000/examples/global/vars/redirect>(URL > <http://127.0.0.1:8000/examples/global/vars/URL>('dashboard')) > response <http://127.0.0.1:8000/examples/global/vars/response>.subtitle = > T <http://127.0.0.1:8000/examples/global/vars/T>("Sign up") > form = SQLFORM > <http://127.0.0.1:8000/examples/global/vars/SQLFORM>(auth.settings.table_user, > separator = '', _class='form-horizontal') > if form.process().accepted: > mail.send('[email protected] <javascript:>', 'Message subject', 'Plain > text body of the message') > return dict(form=form) > > Why not use the built-in registration action? Among other things, the built-in action will log in the user if auth.settings.login_after_registration is True or auth.settings.registration_requires_verification is False (your action does not do that). It also logs the registration event in the auth_event table. If you really feel the need to create your own registration action, it might be a good idea to check the code of the built-in action to see what it does: http://code.google.com/p/web2py/source/browse/gluon/tools.py#2147. Anthony --
