This might just be because I'm setting up the rule incorrectly . . . but what happens is:
I have a rule that has an OR group with 2 condition elements. When I first create a new node of the given content type I get the configurable message 2 times. When I edit an existing node the rule works correctly only giving me the warning once. I'm attaching the rule in case this helps.

Thanks,

V

CommentFileSizeAuthor
habitable_validation.txt5.58 KBVeeLin

Comments

VeeLin’s picture

Component: Rules Core » Rules Engine

I found the problem - when a subsequent rule was executed the rule was re-run. and I was missing an argument in the rule . . . sorry - no help needed. The debug rule evaluation tool is great.

          o 0 ms Content is going to be saved has been invoked.
          o 30.489 ms Included MODULE.rules.inc files.
          o 31.498 ms Executing the rule Infrastructure == non-habitable on rule set Content is going to be saved
          o 31.762 ms Condition Saved content is Value At Risk evaluated to TRUE.
          o 31.985 ms Condition Saved content's field 'field_var_display' has value evaluated to FALSE.
          <strong>o 32.128 ms Executing the rule Habitable Structure NOT Non-Habitable on rule set Content is going to be saved
          o 32.334 ms Condition Saved content is Value At Risk evaluated to TRUE.
          o 32.606 ms Condition Saved content's field 'field_var_display' has value evaluated to TRUE.
          o 32.776 ms Action execution: Populate saved content's field 'field_var_human_life'
          o 32.982 ms Action execution: Show a configurable message on the site</strong>
          o 33.166 ms Executing the rule Calculate sum score of Hazass on rule set Content is going to be saved
          o 33.374 ms Condition saved content is Hazard Assessment Form evaluated to FALSE.
          o 33.461 ms Evaluation of Content is going to be saved has been finished.
    *
          o 0 ms After saving new content has been invoked.
          o 0.341 ms Executing the rule Auto Set Aproval Filed on rule set After saving new content
          o 16.055 ms Loaded variable acting user
          o 16.231 ms Condition User has role(s) evaluated to FALSE.
          o 16.455 ms Condition created content is Value At Risk evaluated to TRUE.
          o 16.631 ms Action execution: Populate created content's field 'field_var_approval'
          o
                + 18.68 ms Content is going to be saved has been invoked.
                + 19.008 ms Executing the rule Infrastructure == non-habitable on rule set Content is going to be saved
                + 19.243 ms Condition Saved content is Value At Risk evaluated to TRUE.
                + 19.465 ms Condition Saved content's field 'field_var_display' has value evaluated to FALSE.
                + 19.607 ms Executing the rule Habitable Structure NOT Non-Habitable on rule set Content is going to be saved
                + 19.812 ms Condition Saved content is Value At Risk evaluated to TRUE.
                + 20.102 ms Condition Saved content's field 'field_var_display' has value evaluated to TRUE.
                + 20.272 ms Action execution: Populate saved content's field 'field_var_human_life'
                + 20.478 ms Action execution: Show a configurable message on the site
                + 20.657 ms Executing the rule Calculate sum score of Hazass on rule set Content is going to be saved
                + 20.863 ms Condition saved content is Hazard Assessment Form evaluated to FALSE.
                + 20.95 ms Evaluation of Content is going to be saved has been finished.
          o 274.651 ms Saved variable created content of type node.
          o 274.757 ms Evaluation of After saving new content has been finished.
    * Value At Risk testing has been created.

V

VeeLin’s picture

Category: bug » support
Status: Active » Fixed
j0rd’s picture

Same bug in Drupal 5 version of workflow-ng.....

Oops. Maybe not. Jumped the gun a little too fast. Appears my duplicate message cause from a ?destination=/frontpage redirect. Causing it to load two pages and then the message to be shown twice on the destination page. Remove the redirect and only 1 message is displayed. This is a Drupal 5 bug and/or feature.

Status: Fixed » Closed (fixed)

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