#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: closed Cleanup/optimization | Version: Component: contrib.admin | 1.5-alpha-1 Severity: Release blocker | Resolution: fixed 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 Russell Keith-Magee <russell@…>): In [changeset:"06b5f5fcb6db2fc20e2d455a34f3f4b0293cfd8c"]: {{{ #!CommitTicketReference repository="" revision="06b5f5fcb6db2fc20e2d455a34f3f4b0293cfd8c" [1.5.X] Corrected tests depending on the error message on the AuthenticationForm. Refs #19368, and the fix introduced in 27f8129d64292868f6a328f7bf9a1bed67967ff3. Backport of 9facca28b619ad94680cf07774ee7a377034ca42 from trunk. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/19368#comment:9> 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.