Thanks for the tip Scoot! On Feb 12, 2:51 pm, "ScottB" <[EMAIL PROTECTED]> wrote: > On Feb 11, 3:42 pm, "voltron" <[EMAIL PROTECTED]> wrote: > > > I plan on using newForms and the auth module for my site. All of the > > examples I have seen involve extracting form data and creating a user > > in the database immediately, how can I "shortcircuit" this process to > > allow one to confirm ones registration per email? > > > What is the preferred "Djangoic" way? I was thinking along the lines > > of creating the user-account, disabling it immediately and sending out > > to the given email address a "hash" of the password , this hash must > > be sent back to the server for comparism per email, I would have to > > parse the mail for this value. > > There's a good article on B-List about this: > > http://www.b-list.org/weblog/2006/09/02/django-tips-user-registration > > I've done something similar, but using newforms. You're on the right > track: > > 1 - create the user, disable the account, generate and store an > activation token (e.g. in a UserProfile model) > 2 - send an email to the user containing a confirmation link with the > token > 3 - user clicks link in email to activate account (e.g. > http://www.example.com/accounts/confirm/voltron/a1b2c3d4e5/) > 4 - once confirmed, enable the account > > Scott
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
