1

In short, I'm simply looking to notify the original author when their node goes from a non-published state to a published state. I have Workbench Moderation enabled if it makes a difference.

I've tried implementing the exact solution that was provided / accepted here (https://drupal.stackexchange.com/a/159103/79465) but can't get it to work for some reason.

Rules

Solved for with the following config: Correct

closed as unclear what you're asking by kiamlaluno Mar 13 '18 at 8:03

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    check this out, might be helpful: groups.drupal.org/node/97454 – longboardnode Mar 13 '18 at 1:14
  • To Chris: please add a phrase to the end which is similar to "What may cause the eMail to NOT be send?". Then flag your own question to ask it to be reopened. – Pierre.Vriens Mar 13 '18 at 8:28
  • @longboardnode thanks for the link! Was able to pick through the examples there and find the solution to my question. – Chris K Mar 13 '18 at 10:45
1

Rules is great, but sometimes also tough to debug if things don't work as you'd expect. In your case, either something unexpected happens in your Rules Conditions, or there is some error in your Rules Action.

There are some typical facilities to do such debugging (further detailed below), but a Keep-It-Super-Simple technique I often use, is my BINGO-trick. A sample of such rule can be found in my answer to "Which Rules condition can be used to email a user when an admin updates their profile?". Stupid, but simple and efficient (I think).

If the above doesn't help, then there are typically 2 ways of more advanced debugging, as further detailed below.

Rules Evaluation Log

Within the Rules settings, experiment a bit with the debugging facilities that come with the rules module. At least have a look at the "Rules Evaluation Log" (to check that the Rules logic being executed, actually matches what you expect that logic to be).

Rules Action to display a value (using devel)

You may also want to (temporary) enable the Devel module, so that you can (temporary) add a Rules Action like "Display a value".

Obviously, make sure that there are no Rules Conditions that would prevent the rules Action(s) from being executed (if needed temporary remove such Rules Conditions).

More info

For way more details about these 2 variations, refer to Rules debugging, as explained in the answer to "How can I display the value of a variable inside a condition?".

  • Thank you -- the Rules evaluation + debugging tips are super helpful as it appears I'm spending all my days in the Rules module lately! – Chris K Mar 13 '18 at 10:48
  • @ChrisK merci for the feedback (and accept/+1) ... So it looks like something "BINGO" did the trick for you also, no? Though I must admit I don't understand what the actual difference is in the party you added below "Solved for with the following config: ...". – Pierre.Vriens Mar 13 '18 at 11:20
  • The difference is that the original was looking at the "After updating existing content" event, whereas the correct/new solution is looking at the "Before saving content" event. – Chris K Mar 13 '18 at 11:27
  • @ChrisK aha, that makes sense. But if the "hold" status of your question ever gets removed, I suggest you MOVE everything starting from ""Solved for with the following config: ..." to a separate answer, and replace that phrase with something like "Using the info provided in the accepted answer, I was able to solve my issue as in the image below (ie using a different rules event". – Pierre.Vriens Mar 13 '18 at 11:37

Not the answer you're looking for? Browse other questions tagged or ask your own question.