Hi,

I use the revisioning module to allw people to write content for approval. It works great. But i try to set up a rule so i can get an email when someone creates a new revision. Am i doing something wrong or is this missing?

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

A rule or even a triggered action should
work.

andeersg’s picture

andeersg commented

I have found that i have to use "Content is updated" or "New content is added" rules triggers. But another problem is that then i don't have access to revisioning tokens.

rdeboer’s picture

rdeboer
Location Melbourne
commented
Title: Rules event when new revision is created? » Rules event when new revision is created? Availability of Revisioning tokens in Rules

Hmmm... I'll have to look into the tokens thing...

andeersg’s picture

andeersg commented

I can try to explain my problem even more:

The reason i want access to those tokens is that i want to set a condition that the revision author is of a certain role. Today i only have access to original author token, and thats wrong if someone else is updating content.

rdeboer’s picture

rdeboer
Location Melbourne
commented
Title: Rules event when new revision is created? Availability of Revisioning tokens in Rules » Availability of Revisioning tokens in Rules
Assigned: Unassigned » rdeboer

FYI: Related to #1566848: Rules "User has role" condition to apply to author/editor of latest revision, not initial revision.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Fixed with latest check-in. 7.x-1.x-dev dated 13 April or later.
Below is a screenshot of the tokens (replacement patterns) available in Rules 7.x-2.3. Note that the tokens "node:revision-author" and "node:revision-created" have subtokens (aka "chained objectes") e.g node:revision-author:name, node:revision-author:mail etc.

Revision tokens in Rules

rdeboer’s picture

rdeboer
Location Melbourne
commented
Status: Active » Fixed
andeersg’s picture

andeersg commented

Thank you so much :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.