You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
subclass django.contrib.auth.admin.UserAdmin and add the enhancements
use django.contrib.admin.sites.AdminSite.unregister(User) to remove the (probably already registered) UserAdmin and then re-register the new, subclassed and enhanced class with django.contrib.admin.sites.AdminSite.register(User, NewAndShinyUserAdmin)
the timing is important here; see https://docs.djangoproject.com/en/2.0/ref/settings/#installed-apps; basically: django-auth-enhancedmust come after auth. (this may be a no-brainer, because at least I only put the default apps before custom ones, but it should be documented, just in case!)
This is basically the start of the development of admin-related functions
of django-auth_enhanced.
Development will be split between modifications of the list-view inside
Django's admin backend and the actual detail view of a single User
object.
However, this will be the branch that represents the pull request that
is going to close#4.
Substitute the default Admin Class for User objects
Brainstorming of features
User
-model is connected toUserEnhancement
The text was updated successfully, but these errors were encountered: