Admin backend cleanup and convenience #99

Closed
opened 3 years ago by mpeltriaux · 1 comments
Owner

Status quo

The admin backend grew during development a little too much.

ToDo

  1. Reevaluate which admin views are really needed for a regular admin and un-register the rest. Keep their ModelAdmin class in code for emergencies.
  2. Add some conviniences to the admin backend:
    1. Search for user on user admin view
    2. Speedup admin detail views (some are very slow!)
    3. Make created or modified fields non-editable and filled by default, once a new model is saved. Only important for backend-only models like ServerMessages
    4. ...
# Status quo The admin backend grew during development a little too much. # ToDo 1. Reevaluate which admin views are really needed for a regular admin and un-register the rest. Keep their `ModelAdmin` class in code for emergencies. 1. Add some conviniences to the admin backend: 1. Search for user on user admin view 1. Speedup admin detail views (some are very slow!) 1. Make `created` or `modified` fields non-editable and filled by default, once a new model is saved. **Only important for backend-only models like `ServerMessages`** 1. ...
mpeltriaux added the
backlog
label 3 years ago
mpeltriaux self-assigned this 3 years ago
mpeltriaux referenced this issue from a commit 3 years ago
Poster
Owner

Merged in #102

# Merged in #102
mpeltriaux closed this issue 3 years ago
Sign in to join this conversation.
Loading…
There is no content yet.