#21431: Django 1.6 GenericRelation admin list_filter regression
---------------------------------+--------------------
Reporter: stephenmcd | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.6
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------
Previously in 1.5 it was possible to have a model A with a GenericRelation
field to a model B that had a ForeignKey to model C, and use the B__C path
in A's admin list_filter.
In 1.6 this fails in django.contrib.admin.util.get_model_from_relation
where the model on the wrong side of the relationship is returned, when
the correct model is available via the parent_model attribute.
I've created a fix and test case here:
https://github.com/django/django/pull/1913
Although as discussed, the fix should probably be different.
--
Ticket URL: <https://code.djangoproject.com/ticket/21431>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.267738ac68e0ee37cfe9b5a09dc03b09%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
