This bug occurs with Revision Moderation. I have a setup which looks like this:

The event for the rule is "Content is going to be saved"

Some conditions are filled (of no relevancy)

The DO is "Enable revision moderation on node" (Permanently apply changes can be on or off)

What happens?

The node gets saved, but two new revisions are created (with the same comment). The most recent one (the one on top) is activated. On the contrary, it is intended that only one revision is created, but it's not activated.

Why does this occur? Is there anything I can do to fix it? Is it the authors of Revision Moderation who should be blamed?

Comments

betamos’s picture

betamos commented
Title: Integration with revision moderation creates two new revisions and activates one of them. » Found something...

Possibly related to #306195: Using trigger and node option results in two revisions...

betamos’s picture

betamos commented
Title: Found something... » Integration with revision moderation creates two new revisions and activates one of them.

[edited title]

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (duplicate)

sounds like a bug related to revision moderation, please look at the issue above or create a new one in its queue.

mitchell’s picture

mitchell commented
Component: Provided module integration » Provided Module Integrations

Updated component.