Use case:
I'd like to move a node nodequeue according to certain conditions. I don't care if it's a new node or an updated one, enough for me that it's saved and has a NID. Without this event I need to make one rule for 'After creating new content' and one for 'After updating new content'.

Patch will follow.

CommentFileSizeAuthor
#1 353168_1_new_save_event.patch1.67 KBamitaibu

Comments

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Status: Active » Needs review
StatusFileSize
new 353168_1_new_save_event.patch1.67 KB

Attached patch.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Needs review » Active

hm, I don't think it's a good idea. If we start doing so, we could add events for a lot of possible combinations of events. So I think we need to find a more generic solution for this kind of improvement.

We could allow the assignment to multiple events - which is a bit problematic for the available variables. But we could do it like when cloning rules - make only variables available which both events provide.

As of now, I'd suggest to just create a rule set and call that from both events, or clone the rules..

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Status: Active » Closed (won't fix)

Setting status.

mitchell’s picture

mitchell commented
Status: Closed (won't fix) » Closed (duplicate)

Marking as duplicate of #364173: Consolidate 'After saving new content' & 'After updating existing content' to 'Node is saved'.

mitchell’s picture

mitchell commented
Component: Provided module integration » Provided Module Integrations

Updated component.