Why is "save post" trigger automatically added...
brisath - September 23, 2009 - 06:07
| Project: | Workflow |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
when I add a trigger for "Make post private to its groups"?
#1
Lots 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.
#2
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.
#3
Yes, deleting the "save post" action would mean that the changes made by the other action would be lost.