To reduce the number of rules for a simple twitter announcement of a node, so I didn't need 2 sets of rules, but only 1 for both the insert and update events.
This adds a new event node_save which is called after the insert/update events so that is will be called when ever node_save is called.
This has meant that instead of 2 triggered rules, I only need to use 1.
| Comment | File | Size | Author |
|---|---|---|---|
| rules_event_node_saved.patch | 1.52 KB | gordon |
Comments
Comment #1
amitaibu#353168: Add "After saving a new or existing content' event - interesting enough is that in the almost same time we both came with the same solution ;)
Comment #2
gordon commentedI am setting this back since the other has been set as don't fix.
Comment #3
fagoI still think it would be the better way to allow the assignment to multiple events to one rule in the long way.
So I'll look to get this implemented asap, if it's too complicated to implement, we still can fallback to that approach.
So I set the issue to "needs work" for now. If you want speed that up and help, I could provide my thoughts on how to implement that.
Comment #4
mitchell commentedAlso marked #353168: Add "After saving a new or existing content' event as duplicate of this issue.
Comment #5
fagoMaybe we should introduce a feature "Custom event", which makes it possible to add new events on the fly? So this won't be needed, however it somehow overlaps with rule sets. I need to think more about that.
Comment #6
mitchell commentedMarked #649328: Sinlge event for saving OR updating content as a duplicate.
Comment #7
gilcpd commentedHey guys
Can someone help me to apply this patch?
I saved the patch on the root of my drupal site : C:\xampp\htdocs\mysite.
I use Cygwin and im typing the following command: c:\cygwin\bin\patch.exe -p0 < C:\xampp\htdocs\mysite\rules_event_node_saved.patch
But is keeps giving me an error that cant find the file to patch "Can't find file to patch at input line 5" .
What am I doing wrong?
Thanks in advance.
Gill
Comment #8
mitchell commentedMarked #479434: Adding node triggers both [add node] and [update node] as a duplicate.
This appears to be a highly recurring issue. If there was a priority between normal and critical, I'd put it there.
Comment #9
giorgio79 commentedComment #10
fagoIn 2.x we can assign a rule to both events at the same time, so I suppose this issue is fixed then?
Comment #11
fagoComment #13
jday commentedwill the ability to assign a rule to both events be back-ported to 6?