hello.. I use the feeds module to import some XML external data in nodes and then run rules on the event "content is going to be saved" to perform some tasks.
I would like to be able to avoid the saving of specific nodes based on certain conditions.
So, basically, is there a way to say rules to STOP the saving of the node that triggered the "content is going to be saved" event?
For those of you that have the same need, an alternative idea could be to set a hidden cck field "to be deleted" and then make a rule "content has been saved" that deletes the node if such field is true... but I wonder if there is a more direct approach to avoid saving of the node at all.

Thank you and cheers!
Antonello

Comments

sylvaticus’s picture

sylvaticus commented
Component: Rules Core » Rules Engine

up.. anybody can just tell me even if it not possible at all or point me on a documentation source??

Gabriel R.’s picture

Gabriel R. commented

Subscribing.

Pierco’s picture

Pierco commented
Component: Rules Engine » Rules Core

Use the following to disable a rule:

$rules_config = rules_config_load('replace_by_rule_machine_name');
$rules_config->active = FALSE;
$rules_config->save();

And set active to TRUE to enable the rule:

$rules_config = rules_config_load('replace_by_rule_machine_name');
$rules_config->active = TRUE;
$rules_config->save();

Edit: sorry, it's for D7 !

sylvaticus’s picture

sylvaticus commented

Hello, I need now to converd my D6 site to D7 and wander if progress has been made on this topic.
I don't (think I) need to "disable" the rule, I just need that, during a "Content is going to be saved" event the rule would be able to stop the saving of the node and possibly leave the user on the the same form.
In D6 I managed with the workaround of flagging the newly saved node with a "to be deleted" field and issue a rule to remove them on the "node has been saved" event, but I wander if this is possible to be achieved more directly now in D7.

Pierco’s picture

Pierco commented

I think you should write a custom processor for feeds and trigger the rules directly from your processor with rules_invoke_event() so you will be able to skip nodes on specific conditions.

orjantorang’s picture

orjantorang commented
Issue summary: View changes

Drupal 6 - activating and deactivating rules by its machine readable name programmatically:

<?php
    $active = TRUE; //or FALSE

    $proxy = rule_load($rule_name);//Machine readable name
    $rule = $proxy->get_rule();
    $rule['#active'] = $active;
    rules_item_save('rules', $rule_name, $rule);
?>
tr’s picture

tr commented
Status: Active » Closed (outdated)