I do not think it can work that way. It has to be token based (a url uuid?) that allows a pre-registered user to complete registration without ability to change email.
On Tuesday, 22 April 2014 04:01:23 UTC-5, Horst Horst wrote: > > I've opened a ticket for the password strength issue, but I don't get the > second part: Users *are* already logged in after they clicked on "Request > Reset Password". > > What I'd wish for is something like a function > > auth.email_complete_registration(user) > > or perhaps > > auth.email_reset_password(user, updateProfile=True) > > which presents a user with the full registration form after clicking the > link, including the password fields. > > Unless there's a better way to achieve this, shall I open an enhancement > request? > > > Am Dienstag, 22. April 2014 00:05:13 UTC+2 schrieb Massimo Di Pierro: >> >> Please open a ticket: >> - the reset password should display password strenght >> - there should be an option to automatically login after reset password. >> >> On Monday, 21 April 2014 16:25:20 UTC-5, Horst Horst wrote: >>> >>> 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.
