Thank you all for your replies. Karen, both good points. pjrharley, I agree with Dennis. If the user is required to re-type their email address, then that in combination with Django's simple built in email validation should be sufficient.
I am using a ModelForms right now. If I remove email_conf from my model, do I add it to the ModelForm, place it in the html form or create a new form to handle it? I guess I'm still a little unsure as to when to use Forms over ModelForms. On Nov 15, 3:51 pm, Dennis Kaarsemaker <den...@kaarsemaker.net> wrote: > On zo, 2009-11-15 at 13:38 -0800, pjrhar...@gmail.com wrote: > > > Also, I have an even simpler suggestion. Don't make the user confirm > > their email. I'm getting fed up with seeing this on forms all over the > > web when it serves no purpose at all. You confirm a password because > > you can't read it back. You don't ask them to confirm every other > > field do you? > > Where I work, we require users to confirm their e-mail address as well > and for a very good reason: too often do people make typos there. For > fields like 'your name' that's not too important but we send them e-mail > with important details and this is an easy measure to make sure less of > this mail bounces :) > > -- > Dennis K. > > The universe tends towards maximum irony. Don't push it. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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=.
