You can probably safely put most of them before define_tables. However, I don't think many actually have to come before define_tables, other than password_min_length, and obviously the ones that set the table names (maybe a couple others). You can always look at the .define_tables method code and see which settings are used there.
Anthony On Tuesday, January 28, 2014 5:08:57 PM UTC-5, User wrote: > > In the welcome application, all auth.settings statements appear after > auth.define_tables statement: > > ## create all tables needed by auth if not custom tables > auth.define_tables(username=False, signature=False) > ## configure email > mail = auth.settings.mailer > mail.settings.server = 'logging' or 'smtp.gmail.com:587' > mail.settings.sender = '[email protected]' > mail.settings.login = 'username:password' > ## configure auth policy > auth.settings.registration_requires_verification = False > auth.settings.registration_requires_approval = False > auth.settings.reset_password_requires_verification = True > > > However, some auth setting statement must occur before auth.define_tables > in order to take effect (such as auth.settings.password_min_length). How > do I know which ones need to come before or after auth.define_tables? Or > can/should they all come before auth.define_tables? > > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
