#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 <timograham@…>):
In [changeset:"20c03399d8fd03484f3ed33d93691c29c2ff5aaf" 20c0339]:
{{{
#!CommitTicketReference repository=""
revision="20c03399d8fd03484f3ed33d93691c29c2ff5aaf"
[1.11.x] Fixed #27998, #28543 -- Restored logging of ManyToManyField
changes in admin's object history.
And prevented ManyToManyField initial data in model forms from being
affected
by subsequent model changes.
Regression in 56a55566a791a11420fe96f745b7489e756fc931.
Partial backport of e5bd585c6eb1e13e2f8aac030b33c077b0b70c05 and
15b465c584f49a1d43b6c18796f83521ee4ffc22 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27998#comment:7>
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/063.502ba84f52536ab0bf96eb656bd3bed8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
