#27998: LogEntry messages do not list m2m fields that were changed when an 
object
is changed via ModelAdmin
-------------------------------+------------------------------------
     Reporter:  ljsjl          |                    Owner:  ljsjl
         Type:  Bug            |                   Status:  closed
    Component:  contrib.admin  |                  Version:  1.10
     Severity:  Normal         |               Resolution:  fixed
     Keywords:                 |             Triage Stage:  Accepted
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+------------------------------------

Comment (by Tim Graham):

 I found that this is a regression in Django 1.10 due to
 ded502024191053475bac811d365ac29dca1db61 and therefore should be fixed in
 the current stable branch, 1.11.x. The fix for #28543 fixes this issue in
 a better way (at the form level, rather than only in the admin) but I'm
 concerned that the approach I've proposed there, changing the return type
 of `ManyToManyField.value_from_object()`, is too risky for a stable
 release. I've proposed an [https://github.com/django/django/pull/8993
 alternate PR] that modifies `model_to_dict()` instead. It restores the
 behavior of `model_to_dict()` returning a list for `ManyToManyField` from
 before 67d984413c9540074e4fe6aa033081a35cf192bc.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/27998#comment:5>
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/063.7810e6ba6269cf43ffb9ff9f1be13b09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to