After you create a node the node is in the creation state, we are able to get the node to show up in a view if we filter on state.

Views adds a
(workflow_node.sid = 1)
to the query (when we filter by "(created)" nodes)

However if we do a
mysql> select * from workflow_node;
Empty set (0.00 sec)

Can this be fixed?

Comments

jvandyk’s picture

jvandyk commented

If you have nodes in the creation state, you are Doing It Wrong™.

The creation state is the state that nodes are in before being created. When a node is created, it moves from being in the creation state to a workflow state. If you have not given permission to the node author to move to at least one workflow state (on the Edit page of the workflow) you might end up with nodes being in the creation state, but I regard this as a misconfigured workflow.

Nodes with no state (for example, nodes that were created before you installed the workflow module) are identified as "No state" in the view.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: bug » support

I changed the category, as the issue reported is not a bug of the module.

Bastlynn’s picture

Bastlynn commented
Status: Active » Closed (works as designed)

What John said: no node should remain in (creation) state longer than a moment's breath before node_save saves it for the first time, triggering nodeapi_insert which moves the node to the first state in the flow.

If your nodes are in (creation) then something is wrong with your install, or you may have configured your workflow so that nodes can't leave the creation state. (In which case they don't get added to workflow_node, since they haven't entered the flow yet).

You want to use views No state to get at these examples, or fix your flow.

Since it's been over a year since the last reply on this, I'm going to assume that you've gotten your situation worked out since then.