I'm trying to create a rule (with the Rules module) that executes when content is changed or created and the revision is pending. It should not execute if the revision is automatically published because a moderator edited it.

Essentially, I want to get an email if a revision is pending so I can publish or reject it.

I've tried the following rule:

On content is going to be saved OR After updating existing content

Revision status of updated content is: Pending

And the revision status is always evaluated to FALSE. I don't know if that is a bug or if I'm creating the rule the wrong way.

Any help would be appreciated.

Comments

rdeboer’s picture

Very old issue -- probably has gone away? Please re-open if this is still an issue in 6.x-3.x-dev. Please specify clearly the steps to reproduce the problem.

rdeboer’s picture

Status: Active » Closed (won't fix)
TheDanScott’s picture

Version: 6.x-3.11 » 6.x-3.13
Status: Closed (won't fix) » Active

Hi there,

I am using the latest "stable" release (6.x.3.13) and this is still an issue for me. Both of the rules "conditions" provided by revisioning always return false on node creation, as this debug output from rules shows:

0.491 ms Condition "Content "created content" has pending revision(s)" evaluated to FALSE.
0.574 ms Condition "Revision status of created content is: Pending" evaluated to FALSE.

Additionally, for updated nodes, the "Revision status of updated content is: Pending" also always returns false, but the ""Content" "updated content" has pending revision(s)" will return TRUE when there is a pending revision.

I guess many people who want email notifications on new pending revisions are also using the workflow module and tie their emails to the workflow. I have a pretty simple workflow and would prefer not to have to use that module in order to simply send an email.

rdeboer’s picture

Will have to have a look... What version of Rules?

TheDanScott’s picture

Hi RdeBoer, thanks for the reply. My rules version is 6.x-1.4.

rdeboer’s picture

Assigned: Unassigned » rdeboer
Status: Active » Fixed

Fixed and checked into repository.
Will be available in development snapshots dated 28-Jan-2012 or later.

Status: Fixed » Closed (fixed)
Issue tags: -rules

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