Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I've looked at this and I can't spot what the change is!
It's probably RTBC, but I'll throw some minor corrections as well:
"Nodequeue\'s integration with workflow_ng module couldn\'t initialize as the Actions module is enabled. Actions module and workflow_ng can\'t be enabled at the same time.'"
hi ezra, i'm not clear how you fixed this. i can't get this off my website:
Nodequeue's integration with workflow_ng module couldn't initialize as the Actions module is enabled. Actions module and workflow_ng can't be enabled at the same time.
Comments
Comment #1
ezra-g commentedI've looked at this and I can't spot what the change is!
It's probably RTBC, but I'll throw some minor corrections as well:
"Nodequeue\'s integration with workflow_ng module couldn\'t initialize as the Actions module is enabled. Actions module and workflow_ng can\'t be enabled at the same time.'"
Comment #2
ezra-g commentedComment #3
ezra-g commentedComment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
jonnystpaul commentedhi ezra, i'm not clear how you fixed this. i can't get this off my website:
Nodequeue's integration with workflow_ng module couldn't initialize as the Actions module is enabled. Actions module and workflow_ng can't be enabled at the same time.
thanks, jon
Comment #6
ezra-g commentedThis issue is about a typo in that message. Please see #489854: Message about workflow/actions collision should not face the end-user.
Comment #7
jonnystpaul commentedok, so there's no patch? it just has to be put up with, right?