when a trigger is assigned to a node creation (a mail and a redirect in my case) the node is inserted in the node table, but not in the event table.
To reproduce just create a "redirect" trigger when a user submit a new node to a "thank you" page and submit an event.
I suppose trigger is send before making the "insert into event_table".
Comments
Comment #1
killes@www.drop.org commentedwhich module does provide this trigger? It seems to me that this report should eb moved to that module's queue.
Comment #2
killes@www.drop.org commentedComment #3
enboig commentedThe trigger modules is supplied by Drupal6 itself.
Comment #4
enboig commentedIf the bug report must be moved to another module, you do it or should I open a new one?
Comment #5
killes@www.drop.org commentedI can confirm that this bug exists.
The problem seems to be that triger_nodeapi is run before event_nodeapi even though the letter t is after e and both have the same weight (0) . If I increase trigger's weight, then it works.
Moving to trigger.module.
Maybe trigger should come with a default weight.
Comment #6
killes@www.drop.org commented15:01 < jmorahan> killes: it's based on the filepath not the filename
15:01 < jmorahan> killes: and modules/trigger is before sites/*/event
That's a classical d'oh.
So the resulution must be to add an extra weight to trigger.
Comment #7
enboig commentedThe fact that trigger should work ok with event module but shouldn't if the modules was called xevent don't seem good to me. Shouldn't the trigger module be the last called module? or at least after any "insert/update/delete" action?
Otherwise, how can this weight be modified? modifying the code? or using a UI?
Comment #8
killes@www.drop.org commentedThere's no Drupal UI, but you can use phpmyadmin to alter the weight column of the system table for the trigger module.
Comment #10
andypostDuplicate of #732542: system_goto_action breaks core APIs