Currently, we can override the queryset used by ModelAdmins.  This is
helpful, since often times the default manager omits instances that
nevertheless belong in the admin.  It seems to me that there's no way
to override the queryset for inlines, though.  Is that correct?
Inlines seem to use the default manager by design, and this is another
expression of the same problem.

i came across this when i couldn't find my child model instances as
inlines in the admin; the default manager for the child model was set
to only show objects for the current site, and i was using the admin
for several sites.

i had posted about this earlier at django-users (http://
groups.google.com/group/django-users/browse_thread/thread/
22781505121558dc/5d6a9595770afb99#5d6a9595770afb99), but now i'm
thinking this has to do with the way the admin contrib app is set up.

Here's a quick app i wrote to demonstrate the issue, with an attempted
workaround (which gets the instances to show up but doesn't allow a
save): http://dpaste.com/80185/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to