It would be great if this module came bundled with an email action for new revisions. Ideally, a group of users (ex. a group of editors) could be notified . New revision emails would not be generated for "approvers" of pending revisions.

Comments

jvandyk’s picture

One could create this easily by copy-paste-renaming the current email action and testing for a new revision in the 'do' op.

webchick’s picture

Status: Active » Postponed

I talked to John VanDyk about this briefly... Actions module needs to be modified so that it can respond to any and all hooks (his project for the plane ride over to Drupalcon ;)) and then this module needs to be modified so it defines a hook to trigger when a new revision is detected.

... I think. ;P

BioALIEN’s picture

Version: master » 5.x-1.x-dev

+1 for this functionality. It only makes sense with a module like this :)

cfennell’s picture

Title: Create New Revision Action » Excellent...

...thanks for the follow-up, I look forward to the fruits of your combined genius ;).

webchick’s picture

Title: Excellent... » Create New Revision Action

Fixing title.

Leeteq’s picture

+1

emdalton’s picture

If the changes are made as described above, would it be possible to trigger an action to place a node back into review state (or some other state) when a new revision is created which needs moderation?

Also, what does it mean that this request is postponed? Has work stopped? Thanks...

mrsocks’s picture

Is there any progress on this?
I could really use this as well.

"Because Drupal doesn't do it" is getting old to many of the users of the site I setup Drupal on.

emdalton’s picture

We are willing to fund this... please see http://drupal.org/node/165686 for details.

emdalton’s picture

Priority: Normal » Critical

How long will this be in "postponed"? We really need this functionality (and as I said before, we're WILLING TO FUND).

webchick’s picture

My arrangement with Lullabot (my employer) means I can't take on paid work outside of our clients. Since none of our active clients are using this module anymore, this puts work on Revision Moderation under "when I have a couple spare hours," which unfortunately probably means mid-November at this point. :(

But feel free to contact any of the other folks who've submitted patches... toemaz, suit4, etc. I'm more than happy to commit stuff if someone takes the time to code it and test.

emdalton’s picture

Thanks. I've tried contacting some of the other developers, with little response, but I'll try again.

toemaz’s picture

Check out a this patch for integration with workflow_ng: http://drupal.org/node/175370

emdalton’s picture

Also, there's a wonderful patch to revision moderation itself which enables Views, which can then generate RSS feeds which can be converted to emails. More at http://drupal.org/node/118666. Thanks, toemaz!

jbjaaz’s picture

I'm a bit confused.

In order to do this, wouldn't you create an additional admin page for mapping actions to certain revision states?

Actions

Revision created -  [ drop down listing all available actions ]
Revision published - [ drop down listing all available actions ]
...

Save Configuration         Reset to defaults

Then wherever the code creates or publishes a revision, check to see if an action has been defined and if so, call the action.

Apologies if I'm missing something, the workflow module is the only other experience I have with actions. That module provides an admin screen for mapping actions to workflow transitions.

fago’s picture

jbjaaz, you could try out the workflow-ng integration, which toemaz has mentioned above.

When content is updated, you can check with conditions, whether a new revision is created and if it's under moderation and fire actions, if the conditions match.

jbjaaz’s picture

Thanks fago. I tried out workflow_ng and managed to get it going properly.

isaac.niebeling’s picture

fago / jbjaaz:

I'm trying to get workflow_ng and revision moderation to work together to let me do an action (send an email, in this case) when a revision that was under moderation has been published (which I think may be what jbjaaz was doing). I'm having a little trouble figuring out the conditions, though. Could one of you point me in the right direction? Here's what I'm doing right now:

Invoked on event: Content has been updated
Conditions: None (right now, I have it sending all the time to try to figure out what to compare in the conditions, but I'm really stuck here)
Actions: Send a mail to an arbitrary mail address

I have it sending the following tokens:

[node:revision_moderation]
[node:revision]
[node:vid]

[node_unchanged:revision_moderation]
[node_unchanged:revision]
[node_unchanged:vid]

So... What am I missing? I only want the email to fire when a revision is published.

Thanks,

Isaac

geek-merlin’s picture

subscribe