Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The current tests are enough to show this you just need to rewrite module_implements :D actions_synchronize badly needs this TRUE. 6.x too. Simply, when you resync you need to reset as well.
| Comment | File | Size | Author |
|---|---|---|---|
| resync_reset.patch | 513 bytes | chx |
Comments
Comment #1
dave reidTested and works fine.
Looking around the actions_synchronize code, I'm not sure even why it needs the $actions_in_code parameter. The only time it isn't given actions_list() for that is when it is called from system_modules_submit. I'll file a separate issue for it, but just wanted to know what you think chx.
Comment #2
dave reidSee #306540: Orphaned assigned actions still triggered and cannot be removed for proposed change to actions_synchronize.
Comment #3
chx commentedThere is one thing for sure, #298600: DBTNG: make module_implements work regardless of bootstrap phase is horribly broken without this.
Comment #4
dave reidSorry about getting off track. I agree with chx that this is needed and the patch is good and tested fine. RTBC
Comment #5
webchickCommitted. Thanks!
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
damien tournoud commentedNeed to get into 6.x too.
Comment #8
gábor hojtsyCommitted to Drupal 6.x, thanks.