#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 Natalia Bidart):
Replying to [comment:12 Antoliny]:
> If it's okay, can I work on this ticket?
> Nessita, if you want to work on it, please feel free to do so. I'd be
happy to follow your lead!
I'm taking a look to have an idea of the fix but you I would love if you
work on this. Otherwise I could use another pair of eyes for what I'll
propose. Right now I'm inclined to change the `required=False` in
`create_usable_password_field` to be `required=True` and then tweak the
checks in `AdminPasswordChangeForm` and `AdminUserCreationForm`. With
that, which would be an "isolated" refactoring, there would be a second
commit considering the `required` in password validation.
What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/36140#comment:13>
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/01070194b25d794b-f0dbbd86-c54d-4b5a-8330-49cff1471da2-000000%40eu-central-1.amazonses.com.
