#3416: Model API documentation section 'Modifying initial Manager QuerySets'
misleads about Admin behaviour
--------------------------+-------------------------------------------------
Reporter: Alex Dedul | Owner: adrian
Status: new | Component: Admin interface
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------+-------------------------------------------------
Changes (by Michael Radziej <[EMAIL PROTECTED]>):
* owner: jacob => adrian
* component: Documentation => Admin interface
* stage: Unreviewed => Accepted
Comment:
Thanks! I see this as a bug in the admin. I made these observations with
your second testcase:
* As you described, the admin shows both objects
* When I click on 'test2', I get a 404.
* In the shell, there is no {{{KnowledgeBaseCategory.objects}}} manager
at all
* In the shell, I see that
{{{models.KnowledgeBaseCategory._meta.admin.manager}}} is the generic
{{{<django.db.models.manager.Manager object at 0xb759c20c>}}}
I suppose that something does not pick up that _meta.admin.manager should
be set to the custom manager.
--
Ticket URL: <http://code.djangoproject.com/ticket/3416#comment:5>
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
-~----------~----~----~----~------~----~------~--~---
