Hello,
I've just try the Editorial Workflow tutorial (http://drupal.org/node/1027546). But when creating the first rule, I didn't see any fields when adding the "data comparaison" condition. When writing directly the field name node:field-workflow, I got an error when validating "The integrity check failed with the following error message: condition data_is: Missing configuration for parameter data."
The modules :
Rules 7.x-2.x-dev (2011-May-19)
Entity 7.x-1.x-dev (2011-May-11)
Comments
Comment #1
iNade commented[bug : I am not the author of the first post, and did not revised it neither.]
It seems that you should load node object before (for example via another new condition : "node type"), then your node:field-XXX will be available.
However it doesn't work neither this way, so subscribing too. I have the last entity (beta10) and rules (beta2) modules.
Ptitoine, you can probably do the thing you want with hook_nodeapi.
Comment #2
iNade commentedComment #3
klausiNo, you don't need to load the node object, as it is passed by the event. And you make use of it in the first condition. Have you done this:
On the resulting page click "Add a condition" and select "Content has type".
If so, then the field should be available for data comparison.
Comment #4
iNade commentedYes, I've done this already, but it seems this bug only happen with multivalues select list (it works has expected with radio or whatsoever).
Do you need any more clues on my settings?
Comment #5
klausiWhy do you have a multi valued select list? The number of values should be 1 (for the tutorial).
Comment #6
dasjoComment #7
mitchell commented>> The number of values should be 1 (for the tutorial).
>> On the resulting page click "Add a condition" and select "Content has type".
>> It seems that you should load node object before (for example via another new condition : "node type"), then your node:field-XXX will be available.
....No, you don't need to load the node object, as it is passed by the event. And you make use of it in the first condition.
Comment #8
mitchell commentedThe changes I thought were necessary from reading the above are in:
http://drupal.org/node/1027546/revisions/view/1479876/2028128
If any further changes are necessary, please open a new task. If any further support is required with the described steps, please open a new issue.