RE: Developing first Django Site -- any advice on co-developing effectively with a professional?

-----Original Message-----
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com]
On Behalf Of Ejah
Sent: Friday, April 20, 2012 11:29 AM
To: Django users
Subject: Re: Developing first Django Site -- any advice on co-developing
effectively with a professional?

Looking at some estimates I wonder if they are fair. F.e. lost password is
part of django-registration, but it might be you want something else.
Anybody some more feedback?
Hth
Ernst


Well, that really depends on the complexity of your registration process.
About a month ago I started developing a website that has the following
requeriments (and more, of course):

- Users can register and must enter required fields like Security Questions,
etc. (django-registration covers that, but it isn't just plug and play. You
need to write a backend or write some tweaks).
- If some user doesn't remember his password, he will have to provide 1) his
email and 2) answer the security questions he selected. It means two
requests to the server: one for confirm the email and obtain the security
Questions associated to that user, and another one to check the security
questions. Well, the resetting password logic is already built-in in
`contrib.auth`.
- Users can change his email. Once the user enters a new email, a
confirmation link will be sent to that email. Once they click on the
confirmation link, the email will be changed. If they never click on the
link, the user will keep using the same email. That isn't covered by
django-registration.

Of course, I could use django-registration for the first part, but then you
would be generating three type of tokens (like
http://example.com/password/reset/<token>):
- The one that generates django-registration
- The one that generates the `password_reset` view under `contrib.auth`
- The one that you will have to generate `manually` when the user wants to
change his email.

We are still beta and testing. In the next phase, the user will have to
confirm the registration by SMS. I think it worth creating your own
confirmation system, and forget about django-registration. Then you will be
using your confirmations when registering (either send the token by email or
sms) and when changing the email :)

My point is that django-registration might not solve your problem all the
time.

Best Regards,
Oscar Mederos

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.