id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 21428,Django 1.6 GenericRelation editable regression,Josh Cartmell,nobody,"Prior to Django 1.6 it was possible to mark a GenericRelation as editable and then add it to the admin fields/fieldsets of a model it was a field of. The following is a simple Django project/app which demonstrates behavior that works under 1.5 but fails under 1.6. It includes a unittest that similarly works under 1.5 but fails under 1.6. https://bitbucket.org/joshcartme/16genericissue I brought this up on the developers mailing list, here is the thread: https://groups.google.com/forum/#!topic/django-developers/Or7LmK17LIU The instigation for this ticket is that Mezzanine makes use of GenericRelations in the way mentioned above. We have been trying to figure out how to bring Django 1.6 support to Mezzanine. Here is the Mezzanine ticket: https://github.com/stephenmcd/mezzanine/issues/745 From that Mezzanine ticket, here is a diff that reverts the changes that cause my simple test case to fail: https://gist.github.com/loic/7427160",Bug,closed,"Database layer (models, ORM)",1.6,Release blocker,fixed,"GenericRelation, ModelForm, Admin, editable",loic@…,Ready for checkin,0,0,0,0,0,0