#36217: post_save signal is not called when LogEntry has Deletion action
-------------------------------------+-------------------------------------
Reporter: smiling-watermelon | Type: Bug
Status: new | Component:
| contrib.admin
Version: 5.1 | Severity: Normal
Keywords: LogEntry Signals | Triage Stage:
post_save | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
I've added a post_save signal for my application to show LogEntry entities
in my logs, but have ran into the following problem:
If I remove some object from admin, LogEntry with Deletion action is
created and stored in the database, but my post_save signal is not called.
I've ensured that other actions are working fine:
- Addition
- Change
So, for some reason only "Deletion" action doesn't cause the `post_save`
signal to be called.
To help reproduce the issue I've created a small [https://github.com
/smiling-watermelon/logentry-bug-demo repository on GitHub] (basically
following Django's documentation on creating a project), and added my
signal there.
If you need any more info from me, just let me know, hopefully the README
is pretty easy to follow and understand.
The exact Django version I've been using is 5.1.6, in both - the demo
(though there it's not pinned!) and my real project.
--
Ticket URL: <https://code.djangoproject.com/ticket/36217>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070195480b837f-27b3b6fd-6ee2-43a5-a424-c4bbe0c757a1-000000%40eu-central-1.amazonses.com.
