#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 GitHub <noreply@…>):
In [changeset:"e5bd585c6eb1e13e2f8aac030b33c077b0b70c05" e5bd585]:
{{{
#!CommitTicketReference repository=""
revision="e5bd585c6eb1e13e2f8aac030b33c077b0b70c05"
Fixed #28543 -- Prevented ManyToManyField.value_from_object() from being
lazy.
Previously, it was a QuerySet which could reevaluate to a new value if the
model's data changes. This is inconsistent with other
Field.value_from_object()
methods.
This allows reverting the fix in the admin for refs #27998.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27998#comment:6>
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.7698686a7b8ec4c5cab60fa19f210604%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
