Opened 17 years ago
Closed 17 years ago
#4857 closed (worksforme)
Confusion about is_active
Reported by: | anonymous | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
It seems to me that the is_active (in Admin->Auth->Users) is missleading.
The docs say: Designates whether this account can be used to log in. Set this flag to False instead of deleting accounts.
Which seems that this is independent of the admin site.
The Admin itself says: Designates whether this user can log into the Django admin. Unselect this instead of deleting accounts.
But for this we already have staff status, haven't we?
Note:
See TracTickets
for help on using tickets.
It seems clear enough to me: you use it "instead of deleting accounts". Perhaps the Admin wording could be fixed but it's a very minor issue. If anyone cares enough to write a patch for that, feel free to reopen.