Opened 6 years ago
Last modified 21 months ago
#30402 closed Bug
Django default_site admin configuration doesn't register anything — at Version 1
Reported by: | Przemek Pawlas | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Steps:
- I have project X with app Y, which has admin folder with site.py and multiple specific_model.py.
- In site.py I extend AdminSite with SocialAuthAdminSite.
- In specific_model.py files I use admin.site.register(Model, ModelAdmin)
- In project/apps.py I extend AdminConfig with SocialAuthAdminConfig which has default_site = 'X.Y.admin.site.SocialAuthAdminSite'
- In settings I load X.apps.SocialAuthAdminConfig (tried at the beginnning, end, etc. - I don't think it matters)
Expected:
Admin classes for models should be registered like they were before I made edits to use default_site (before I just assigned the site to a variable and used that).
Actual:
Admin classes for models are not registered. The customized admin works otherwise though.
Note:
See TracTickets
for help on using tickets.