Where did the actions go?
| Project: | Workflow |
| Version: | 5.x-2.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | patch (code needs review) |
I don't know if I am missing something or what, but when had version 5x-1.x installed, the actions to publish and unpublish nodes as well as a group of others were listed as actions in the actions area of workflow. I wanted to automatically publish/unpublish nodes when it changed workflow states. Everything is there, and works correctly. But on 5.x-2 they are not an option.
The Node action items of publish node, and unpublish node are not options in the actions (now Triggers area) pop-up even though they are listed on the actions page. What step am I missing here? Is this possible, to do or do I have to stick with 5.x-1.x to have this. Again, I must be missing a step here but any help would be appreciated.
See the attached to see what is listed as workflow actions and what are the actions in the system.
| Attachment | Size |
|---|---|
| triggers.png | 54.33 KB |
| actions.png | 54.21 KB |
#1
Please read the Actions in Contexts section here: http://drupal.org/project/actions
#2
So according to that, it says that it can't be done? Being the action is not in the context of the workflow, it won't show up? I don't understand enough to know what keeps it from showing up on one list since it does on another :)
#3
From that page: "To be able to assign any action to any context (as you could in 5.x-1.x), use the triggerunlock module.
"
#4
Try installing the trigger unlock module.
http://drupal.org/project/triggerunlock
Although it says it is for Drupal 6 in will also work in Drupal. It will make all actions available to all contexts.
#5
That works, thanks for the help!
#6
So this module is currently completely unusable without triggerunlock. This should at the very least be documented on the Workflow page, but honestly, it should probably just be a dependency of the workflow module.
Here's a patch.
#7
Honestly I think the solution to this is to introduce a toggle into the actions module between "Show recommended actions" and "Show all actions" or something. "Training wheels on / Training wheels off?"
#8
That could also work, but then the install hook of this module really ought to switch that on. This module's completely unusable otherwise, and people don't read docs.
#9
Okay, seriously, this needs to be documented in big bold letters on the project page for Workflow. I burned HOURS trying to figure out why my actions/workflow setup wasn't working the way it does in the tutorials, including the one at Lullabot. Holy cow! Workflow is now useless without Triggerunlock ... definitely make Truggerunlock a dependency of Workflow.
#10
I fully support this - just wasted a lot of time myself!
#11
Wasted a lot of time too :(