Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#15377 closed (wontfix)

last_login should reflect real activity

Reported by: alper Owned by: nobody
Component: contrib.auth Version: 1.2
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

It looks like User.last_login is only triggered on a real login action. This does not in any way reflect real activity on a site if somebody saves their session.

Request: last_active field which is updated on a much more granular level on each request or such.

Change History (2)

comment:1 Changed 4 years ago by Honza_Kral

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

This is out of scope for django. It would be a backwards incompatible change and could cause problems with high traffic sites. Since there is nothing stopping you from tracking last user activity by some other means I am marking this as wontfix.

comment:2 Changed 4 years ago by schinckel

As a tip: you could use a middleware to do this, very easily.

Note: See TracTickets for help on using tickets.
Back to Top