Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Thanks for the explanation. I assume I should just leave it as is, and not delete any of these "save post" triggers because it won't interfere with the intended action.
Comments
Comment #1
jweowu commentedLots of actions update a node object in memory, but do not save it to the database.
They flag this by setting 'changes_node_property' in their hook_action_info() definition.
trigger_assign_form_submit() picks up on that property, and appends node_save_action to the list of actions.
Comment #2
brisath commentedThanks for the explanation. I assume I should just leave it as is, and not delete any of these "save post" triggers because it won't interfere with the intended action.
Comment #3
jweowu commentedYes, deleting the "save post" action would mean that the changes made by the other action would be lost.