Thanks, Massimo, what I ended up doing so far is: 1. Pre-registering users with register_bare(), using a random password and an empty user name 2. Sending out a password reset mail like you wrote 3. After the user changed the password, on the subsequent call of index(), having the app check whether the user name is empty and redirect to user/profile
This works, but the user experience for new users is less than ideal, as they get to see two forms in a row. In addition, the reset_password form lacks the nice password strength coloring feature - and the new users choose their first password here. Do you see a way to present them with the actual register form or an equivalent single form? Am Montag, 10. März 2014 02:02:52 UTC+1 schrieb Massimo Di Pierro: > > One way is to create accounts in auth.auth_user and the call > > for user in newly_registered_users: > auth.messages.reset_password = "I have shared a document with you click > on the link %(link)s to reset your password, your document is ..... bla bla > bla" > auth.email_reset_password(user) > > On Friday, 7 March 2014 08:14:21 UTC-6, Horst Horst wrote: >> >> I'd like to implement a feature similar to sharing Google docs or >> Dropbox: If you share something with a non-registered user, he gets a >> notification email, but once he signed up, the permissions are already in >> place. >> >> Programmatically registering users should be no problem, but how can I >> show the registration form on their first visit, and have it not complain >> about the email being already present? >> > -- 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/d/optout.
