Prevent Node from being saved

I too am looking for similar functionality.
I need to "not save" the content and issue a system message saying why the content cannot be saved.

I figured it out. heres how:

Create rule of type "content is going to be saved"

Add condition "if content type is xxx"
And whatever other condition you require to return true or false.

Add action "system page redirect" and set configuration to redirect to the same page.
Set configuration of above action to "immediately issue redirect".
This will stop the process of node creation in its tracks and send the user back to the node creation page.

to issue an error notice to the user.
You can do this by adding a "set configurable system message" action BEFORE the page redirect action.

Hope this helps someone else.

This really seems like an issue that shouldn't be solved with Rules. (At least as the module works right now.)

If you want to prevent users from entering certain combinations of values in a form, it makes much more sense to have a custom validation function. This *might* be possible to do with Rules Forms Support in D6, but in D7 it would require some custom coding. (There might be some modules allowing you to build custom validators, but I don't know them.)

Also: If you just want to prevent values above a certain threshold, you could use the "maximum" settings available for number fields.

Marking this as "won't fix". Sorry.

Hi,
@voodoo.child, for me your solution works except in one detail: all the data introduced by the user before trying to save the node dissapears, so they would have to introduce it all again :(

@Itangalo, how could I implement a custom validation function for this purpose? Any tip? I am not an expert yet with hooks, etc.

Thank you.

I already found the solution :)
http://groups.drupal.org/node/25403

@estebant: I was thinking more of writing a custom function in PHP, but if you found a way to do this with Rules that is just fine. Great!

@estebant: great. thanks for updating with the rules validation option.

While this may not be the best or most efficient way, you could always include an action to delete the node immediately after it was created, and redirect the user back to the node creation page. I am doing that right now for a workaround to #1918216: Resource Conflicts are not detected in certain cases, though it would probably be better if I learned some PHP and wrote a validation function.

@v-a-1
Your recipe is for D6, but I have no Ideas how to interrupt saving a node in D7 by Rules.

related #1780526: Support Entity Validation in D8

Changed version by accident.

Working for me using "Before Saving Content" and a PHP custom code with drupal_goto() function inside (D7)