- 🇬🇧United Kingdom malcomio
As far as I can see there isn't a way to do this - ideally it should be configurable - see ✨ UI to control which transitions create events Active
I'm using this module together with the “parent” DANSE project and have my content type configured like this:
<!--break-->However soon realized that danse_event records are generated twice per each save of the node. The first (with a lower entity ID) is the one about the moderation status change but right after it, the second one is still about the node update.
I wouldn't care about them too much but the problem is that the danse_notification records reference the simple “update” event (which is less specific and therefore misses the valuable information about the exact moderation state involved) instead of the status change event.
My question is that are there any options either from configurational side via the UI or directly from code to prevent these “update” events from creation ONLY when a moderation state event is already created? I want to keep them being created when no moderation-related modification happens on the node (eg. author or title field changes).
Active
2.0
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As far as I can see there isn't a way to do this - ideally it should be configurable - see ✨ UI to control which transitions create events Active