On Tue, Nov 13, 2012 at 8:17 AM, azurIt <azu...@pobox.sk> wrote: > Hi, > > i have the following problem: > User is choosing a login in first step (login is validated and is checked > if it's available) and is filling up some other data in second step. > Finally, i'm trying to create a new account BUT the login can be already > taken (there's a little time frame between 1 and 2 step so it's possible). > How can i show the first step to the user and ask him to choose another > login WITHOUT loosing any data from second step? Thxn for suggestions. > > azur >
You really need to create the account, thus reserving the login (username?) in step 1, when the check succeeds (in fact, the test probably should be an attempt to create the account, whose failure is what kicks the user back to choose another login). You keep a creation date and note (perhaps via the lack of a validated email address) whether registration has been completed. Then periodically run a daemon that queries for account creation attempts that are taking too long to complete, and delete them. Bill -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
