#36140: UserCreationForm doesn't allow empty password even if password fields
are
specified as "not required"
-------------------------------------+-------------------------------------
Reporter: buffgecko12 | Owner: (none)
Type: Bug | Status: new
Component: contrib.auth | Version: 5.1
Severity: Release blocker | Resolution:
Keywords: form | Triage Stage: Accepted
usercreationform validation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Antoliny):
This issue is related to passwords, I believe it should be designed as
defensively as possible.
Unless there is a clear intention from the user (such as having
usable_password set to None in the author's form), usable_password should
remain True. This aspect is not covered in the above changes.
{{{
if hasattr(self, "usable_password") and self.usable_password == None:
...
}}}
I think there might be another condition needed as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/36140#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194b163b314-376377cd-372f-40d0-9e4d-d7b7753b39fa-000000%40eu-central-1.amazonses.com.