#19368: Custom User without username and with USERNAME_FIELD = 'email', but
still
see username error message at the admin login page
-------------------------------------+-------------------------------------
Reporter: un33k | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version:
Component: contrib.admin | 1.5-alpha-1
Severity: Release blocker | Resolution:
Keywords: custom user, | Triage Stage: Ready for
USERNAME_FIELD, username | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by ptone):
I'd only add that the language should be changed to say "Note that fields
*may* be case-sensitive" which is sort of a cop out - but we now can't
know the implementation, and it at least gives the user a heads up if they
are forgetting that - esp for hidden PW field.
--
Ticket URL: <https://code.djangoproject.com/ticket/19368#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
