#21013: Admin history should consider ModelAdmin.get_queryset
-------------------------------+--------------------
     Reporter:  jonash         |      Owner:  nobody
         Type:  Uncategorized  |     Status:  new
    Component:  Uncategorized  |    Version:  1.5
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+--------------------
 * Model with custom default manager that excludes some objects
 * ModelAdmin with custom `get_queryset` that includes more objects than
 the manager
 * History view throws 404 for any objects that aren't included the default
 manager because it doesn't consider the ModelAdmin's `get_queryset`
 method.

 Test an fix attached. Tests are probably in the wrong place and need to be
 moved.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21013>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.1d5eba06e603ce9465e471112ab60aa9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to