#36217: post_save signal is not called when LogEntry has Deletion action
-------------------------------------+-------------------------------------
Reporter: smiling-watermelon | Owner: Antoliny
Type: Bug | Status: closed
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution: fixed
Keywords: LogEntry Signals | Triage Stage: Ready for
post_save | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"5997fdc9214eafaaf2fadc065f1d2ced34641598" 5997fdc9]:
{{{#!CommitTicketReference repository=""
revision="5997fdc9214eafaaf2fadc065f1d2ced34641598"
[5.2.x] Fixed #36217 -- Restored pre_save/post_save signal emission via
LogEntry.save() for single-object deletion in the admin.
Regression in 40b3975e7d3e1464a733c69171ad7d38f8814280.
Thanks smiling-watermelon for the report.
Co-authored-by: Sarah Boyce <42296566+sarahbo...@users.noreply.github.com>
Backport of c09bceef68e5abb79accedd12dade16aa6577a09 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36217#comment:10>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701956084382e-d9dfafe3-9b9c-40bf-b77d-88c573548727-000000%40eu-central-1.amazonses.com.
