Add admin.site._registry manipulation methods
|Reported by:||Rob Hudson||Owned by:||anonymous|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
This is a feature request...
Currently, one can unregister a model from the admin and register it again with a new ModelAdmin. The problem I'm anticipating is when 2 or more apps want to add ModelAdmin options to a Model and the last one wins.
Not to point out a specific 3rd party app, but this is an easily contrived example... If I have my own apps and one of them unregisters the User model's ModelAdmin and registers its own that, say, adds the
is_superuser to the list_display. Then if I add the django-openid app that (currently) also unregisters the User model's ModelAdmin and registers its own that adds an inline to a ManyToManyField for the OpenID associations tied to that user. If django-openid is after my app in the INSTALLED_APPS list, I lose my list_display override. And if my app is after the django-openid app, I lose the OpenID associations inlines. (See: http://code.google.com/p/django-openid/source/browse/trunk/django_openid/admin.py)
It's possible currently to write the unregistration/registration such that this doesn't happen, but it relies on pulling the ModelAdmin out of the "private" _registry dictionary in the admin.site class. For example:
useradmin = admin.site._registry.get(User, None) if useradmin: useradmin.list_display = useradmin.list_display + ('is_superuser',) else: class MyUserAdmin(AuthUserAdmin): list_display = ('username', 'email', 'first_name', 'last_name', 'is_staff', 'is_superuser') admin.site.register(User, MyUserAdmin)
I can think of a few ways of fixing this, from least involved to more involved:
- At the very least I think it would be nice if the internal
_registrydictionary didn't have the prepended underscore to signify that it is a private variable not to be touched, so one doesn't feel dirty doing something like this.
- I think it would be a bit cleaner if there were methods to lookup, get, and update this dict and keep it as a private dict. For example, something like
- Along with 2, provide methods to update common ModelAdmin options, like
list_display. This one is definitely venturing into debatable area, but something like
useradmin.list_display.add('is_superuser')takes much away from this feeling so "monkey patchy".
Change History (5)
comment:3 Changed 5 years ago by
|Triage Stage:||Design decision needed → Accepted|
comment:4 Changed 3 years ago by
|Owner:||changed from nobody to anonymous|
|Status:||new → assigned|