This issue occurs with installation that use multiple workflows, and a stage name is not unique between all workflows. The current logic finds the first matching stage in any workflow, and attempts to use that in updating the nodes. This fails when the first matching stage is in a workflow that is not valid for the node.

For example:
Two workflows are created: StoryFlow and PageFlow. Storyflow is created first. Nodes of type Story are assigned to workflow StoryFlow. Nodes of type Page are assigned to workflow PageFlow. Attempting to set all unpublished nodes to status (creation) only works for nodes of type StoryFlow.

Comments

achbed’s picture

achbed commented
Status: Active » Closed (fixed)

Fixed. Previously, the search for a state ID was done once per request and had no reference to node type nor the workflow assigned to that type. Now, the search is done on a per-node basis. This allows for proper handling of the same state name in different workflows for different node types (ie, (creation) is common to all workflows).

Note that we still only have a single flag for node selection: publish state. This should be addressed in a future release.