I fought today with this specific issue (whatever I did, I was not able to get registrations to having a pending state, but all new registrations ended up being logged in immediately.)
The culprit in my case turned out to be an innocent looking row that somehow had been inserted at the beginning of controllers/default.py: auth=Auth(db) This basically resets the auth object to its default state (I assume). Just thought to add this here as a one potential solution in case there are people having similar problems. -Teemu On Thursday, August 20, 2015 at 8:09:26 PM UTC+3, Karl-Thomas Schmidt wrote: > > Thanks, Jaime Sempere, > > i tried this in all kinds of variations. Still no pending registrations. > And still immediately logged in after registering. > > Some strange things besides: Having done an update of web2py to new 2.12,3 > it still shows 2.11.2-stable+timestamp.2015.05.30.16.33.24 and recommends > again updating. > > Having desperatly seeked for my failure i ended up in a very fresh > downloaded > 2.12.3 and it STILL shows the old version. > a "grep -r <old version string>" does what one would expect: it shows > nothing. > > If it happens that my administrative interface sessions times out, i get a > messed up screen where the relogin form displays somewhere right to the > middle. > Logging in with this forms results in an unkown error. Clicking this > ticket > takes my back to admin interface flashing that the error ticket is > unvalid. > > This behaviour showed up first time with old version 2.11.2- > stable+timestamp.2015.05.30.16.33.24 > > This drives me crazy. > And led me to stupid things, like restarting nginx 1.2.1 and uwsgi 2.0.9 > > Meanwhile i draw the conclusion that the internet hates me, german Debian > Wheezy servers are gaga and Massimo does not want me to use web2py. > > Can you pass me an address of a good doctor? > > > > Am Mittwoch, 19. August 2015, 15:38:47 schrieb Jaime Sempere: > > Im using same web2py version and python 2.7.x > > > > My db.py works (user is inserted on db marked as 'pending') with this > > configuration: > > > > from gluon.tools import Auth, Service, PluginManager > > > > auth = Auth(db) > > > > service = Service() plugins = PluginManager() > > > > ## create all tables needed by auth if not custom tables > > auth.define_tables(username=False, signature=False) > > > > ## configure auth policy > > auth.settings.registration_requires_verification = False > > auth.settings.registration_requires_approval = True > > auth.settings.login_after_registration = False > > auth.settings.reset_password_requires_verification = True > > > > > > Try with all this configuration to see if it works... > > > > > > El miércoles, 19 de agosto de 2015, 15:22:32 (UTC+2), Karl-Thomas > Schmidt > > > > escribió: > > > Hi@ all, > > > > > > Having this lines in db.py > > > auth = Auth(db) > > > auth.settings.registration_requires_approval = True > > > auth.settings.login_after_registration = False > > > a new registration immediatly logs in and corresponding db field is > still > > > empty. > > > > > > Running 2.11.2-stable+timestamp.2015.05.30.16.33.24 (Running on > > > nginx/1.2.1, > > > Python 2.7.3) > > > > > > What do i miss here? > > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
