On Feb 10, 5:22 am, Roboto <robc...@gmail.com> wrote:
> class userForm(ModelForm):
OT : Python's naming convention is "UserForm"
> first_name = CharField(label='First Name')
> last_name = CharField(label='Last Name')
> email = CharField(label='Your Email')
> password = CharField(label='New Password', widget=PasswordInput())
> def clean(self):
> from django.core.exceptions import ValidationError
OT, but please keep your imports at the beginning of the module unless
you have a very strong reason to do otherwise.
> try:
> user = User.objects.get(username=email)
This should raise a NameError here since 'email' is not defined
(unless of course there's an 'email' identifier defined in the global
(module) scope).
> raise ValidationError("account already exists")
> except User.DoesNotExist:
> return None
Form.clean is supposed to return cleaned_data. Also, ModelForm.clean
performs some validation too, so you should call it somewhere in your
code (preferably at the beginning I'd say).
wrt/ what you describe, I don't see any reason your clean() method
wouldn't get called during validation (unless some exception breaks
the normal flow before you get there).
--
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=en.
