Nothing besides adding a bunch of extra fields:
auth.settings.extra_fields[auth.settings.table_user_name]= [
Field("nickname", "string", length=80),
Field("city", "string", length=80),
Field("country", "string", length=80),
]
Am Freitag, 16. Mai 2014 15:05:53 UTC+2 schrieb Anthony:
>
> Have you customized the auth_user table in any way (in particular,
> anything that would prevent the default validators from being added to the
> email field)?
>
> On Friday, May 16, 2014 8:05:22 AM UTC-4, Horst Horst wrote:
>>
>> It seems (at least in my case) the conversion to lowercase before storing
>> the email address in the database doesn't happen. I've just tried it with
>> the auth settings below, and the auth.user record contains the email as
>> registered. Perhaps there's a different control flow when using email
>> verification?
>>
>> auth.settings.email_case_sensitive = False
>> mail=auth.settings.mailer
>> mail.settings.server = <...>
>> mail.settings.sender = <...>
>> mail.settings.login = <...>
>>
>> auth.settings.registration_requires_verification = not
>> request.is_local
>> auth.settings.registration_requires_approval = False
>> auth.settings.reset_password_requires_verification = True
>> auth.messages.email_sent = 'Confirmation mail sent. Please check your
>> email.'
>> auth.messages.verify_email = 'Thank you for joining %s,
>> %%(first_name)s! Please click on the link %%(link)s to verify your email
>> address.' %DOMAIN_NAME
>>
>> auth.settings.login_next = URL('user_home')
>>
>>
>> Am Freitag, 16. Mai 2014 13:40:57 UTC+2 schrieb Anthony:
>>>
>>> Did you set email_case_sensitive = False *after* those users had
>>> already registered? With that setting, upon registration, it converts the
>>> email to lowercase before storing in the database, and then on login, it
>>> looks for the lowercase version of the email in the database. Try
>>> converting all email addresses already in the database to lowercase and see
>>> if it works then.
>>>
>>> Anthony
>>>
>>> On Friday, May 16, 2014 6:48:25 AM UTC-4, Horst Horst wrote:
>>>>
>>>> I'm running web2py 2.9.5 and set auth.settings.email_case_sensitive to
>>>> False in my app, because I thought it'd be a good idea.
>>>>
>>>> Now I have a bunch of users complaining that they can't log in, and
>>>> figured out that they registered with an email address which contains
>>>> capital letters. I tried myself and it seems that the case insensitivity
>>>> only works if the email address is all-lowercase during registration.
>>>> Otherwise even identical spelling on registration and login leads to an
>>>> "Invalid Login."
>>>>
>>>> Shall I open a ticket?
>>>>
>>>>
--
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.
