#26823: auth signal receiver update_last_login not compatible with custom user
models that have no last_login field
--------------------------------+------------------------------------
Reporter: Harry Percival | Owner: nobody
Type: Bug | Status: closed
Component: contrib.auth | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"eedc88bd4a8468c2a0daa8346c9b57183dd77782" eedc88bd]:
{{{
#!CommitTicketReference repository=""
revision="eedc88bd4a8468c2a0daa8346c9b57183dd77782"
Fixed #26823 -- Prevented update_last_login signal receiver from crashing
if User model doesn't have last_login field.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26823#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.d4b5610dfc6cc389529eb43fc5317528%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
