Hello, I'm using the following conditions in a rule that triggers as 'Content is going to be saved':

Created content is CONTENT_TYPE_X
AND
Created content is new
AND
Created content's field 'FIELD_X' has value

And using this to trigger

Populate saved content's field 'FIELD_Y'

I suspect that the rule gets triggered whether or not the content is new content, because I'm seeing the FIELD_Y value change when I edit existing content in the same way I would expect it to change when saving new content. However, I'm not seeing anything in the rule evaluation log that indicates the rule has been triggered.

I 'm assuming that 'Created content is new' indicates that a node is just being created as opposed to an existing node that is being resaved after editing. I don't see anything in the documentation that suggests otherwise.

Have I interpreted 'Created content is new' incorrectly? Do yo have any insight on what might be causing this issue?

Many thanks for your time.

Comments

mitchell’s picture

mitchell commented
Title: Rule firing on existing content despite 'content is new' condition » Help with 'content is new' condition
Category: bug » support
mitchell’s picture

mitchell commented
Component: Rules Engine » Rules Core
Status: Active » Closed (won't fix)

Thank you for submitting a support request / issue for Rules 1. Sorry it was not attended to earlier; I hope you found the information you were seeking in another resource, such as the Rules Drupal 6 documentation.

Because it has been a while since it was first submitted, I'm closing it to clear up space. However, if you would still like to submit another support request or help answer others support requests, your efforts would be welcomed and appreciated.