#7852: Cross-application model inheritence broken after newforms-admin merge
---------------------------------------+------------------------------------
Reporter: jbalonso | Owner: nobody
Status: closed | Milestone:
Component: Database wrapper | Version: SVN
Resolution: invalid | Keywords: model inheritance
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by brosner):
* status: new => closed
* resolution: => invalid
Comment:
There already is a convention for registering models with the admin
interface that does not involve models.py. Originally models.py was the
only decently safe route before an admin.py module was introduced for
applications. All ```ModelAdmin``` classes should be placed in an admin.py
file in the app. Registration with the default ```AdminSite``` instance
should be done there only. If you have a need for your own ```AdminSite```
then do so at a project-level admin.py and do registration there. The
```admin.autodiscover()``` function will take care of doing the imports on
the admin.py modules of the ```INSTALLED_APPS```. See
[http://www.djangoproject.com/documentation/admin/#hooking-adminsite-
instances-into-your-urlconf the documentation] for more information. I am
assuming you are seeing ```AlreadyRegistered``` exceptions, if so keep
this closed, otherwise re-open with specific details.
--
Ticket URL: <http://code.djangoproject.com/ticket/7852#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
