Have a look at the 'make_random_password' method in 'django/contrib/auth/model.py' - it's the same principle there. In case you already have a extended user profile, I would store the activation string there. Otherwise I'd make a dedicated model to store them with a link to the user, the string and a generation date. If someone calls the link, then just compare the date field with the current server time.
Jesore patrickk wrote: >sorry for being stressful - but could you give an example: >how to generate that string? >where do you store it and how handle the expiration? > >thanks, >patrick > >Am 19.07.2006 um 09:40 schrieb Kenneth Gonsalves: > > > >>On 19-Jul-06, at 12:57 PM, patrickk wrote: >> >> >> >>>that makes sense to me. >>> >>>still, I have 2 more questions: >>>1. what kind of query do you use for email confirmation (how do you >>>generate it)? anything special to consider here? I did use a >>>combination of a password-hash with the date_joined so far, but I´m >>>not sure that´s the right way to go. >>>2. I guess you use a random password first and then override that >>>password, right? >>> >>> >>you create a url with a random string - usually timed to expire in a >>few hours. The user clicks on that url and gets his confirmation >>screen where he can set his password >> >>-- >> >>regards >>kg >>http://lawgon.livejournal.com >>http://nrcfosshelpline.in/web/ >> >> >> >> >> > > >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
