I would play around with this: auth.settings.register_next
First off, I wouldn't 'pre-register' my users. Rather, I would put their email address in a table and have it sit there until they register. In the controller pointed to by the statement above I'd then check to see if the email for the new registration was in the table. If so, setup the required permissions then. Once that controller is done, redirect them where they need to go. ...just my thoughts on your issue. -Jim On Friday, March 7, 2014 8:14:21 AM 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.
