Currently the only way to manage the order in which triggers are ordered is to unassign triggers you want to move to the bottom of the action, and readd them.
There should be an interface for organizing the order in which triggers are fired. This seems like a pretty basic feature which anyone dealing with triggers will probably run into. Especially if you want to do something to a node and then something else, i.e. you want to turn off an action, and then save it. This is a problem right now with revision moderation, workflow and triggers, and I am sure it will come up else where.
Use case:
you want to save a node, and then turn revision moderation on. If you were to add these in the wrong order the node would not get published, but instead would be added to revision moderation. after which it would then publish an old version. Not a very smooth move.
Comments
Comment #1
not_Dries_Buytaert commentedAgree. Currently, newly added operations/ actions are added to the bottom of the list and the order for executing operations/ actions is from top to bottom. If 'drag and drop' (similar to how menu items can be rearranged) is too difficult to implement, adding a configurable 'weight' for each assigned operation would be another solution.
Changed to version to 6.13, since this request is useful for these (and future) versions, as well.