On Tue, Nov 13, 2012 at 9:07 AM, azurIt <azu...@pobox.sk> wrote: > >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. > > > I'm creating account in the last step when i have all needed info for > doing it. There must be a way how to redirect user to specified step > without loosing any data. > > azur > > Separate step is separate browser interaction. Even if you did this with AJAX, other requests can come in in between actions. Other users don't get blocked from accessing the site just because one is in the middle of registering. Sorry, but that's the way the web works.
By the way, you don't need anything else to create the account. You can fill in any required fields with place holder values, and leave login disabled until you get your real minimum. 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.
