Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.To reproduce in https://test.seehallen.drupal.mobimo.lakedrops.com/:
- DANSE is configured properly and all possible events are configured for a content type (see attachment).
- Create a new content for content type EVENT and save it as draft. There is no entry in the DANSE Event logs
- Open the content and set it to publish (do not publish it in the moderation dialog). Save the content. There are two entries in the log for update and publish
- Publishing the content in the moderation dialog also does not create a log entry.
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot 2020-09-08 at 10.56.45.png | 169.55 KB | danielspeicher |
Comments
Comment #2
danielspeicher commentedAdditional information: In our demo installation https://test.demo.drupal.mobimo.lakedrops.com/ it works a s expected. The configuration seems to be the same from my point of view.
Comment #3
jurgenhaasConfirmed, I can see the same effect. Will try and debug that locally.
Comment #4
danielspeicher commentedSame surveillance in Kriens. In AQA it works as expected.
Comment #5
jurgenhaasSeems like I found the difference: seehallen and kriens have media fields that are required which means we have to open other forms during node editing which seems to break something in the logic. On the other hand, demo and aqa don't have such required fields, and that's why they work just fine.
So, I have to find out why this breaks the logic. And at the same time, I realized that we only react on content entity changes in their edit form but not on other ways of changing them, like e.g. the content moderation form or even changes through the API. I'll have to see why we've done it that way and try to find a way of fixing this.
Comment #7
jurgenhaasWe are now storing values between form builder and submit handler differently which survives ajax calls and other embedded forms. That fixes the original issue. Regarding the other issue to create events also for entity changes without their edit form, we'll open a new issue.