I created a new node (node/add-form), but after saving there is no state stored in databasetable workflow_node, so no state is shown in views.
After saving the same node via node/edit-form without editing of any field, the first state is stored.
I created a new node (node/add-form), but after saving there is no state stored in databasetable workflow_node, so no state is shown in views.
After saving the same node via node/edit-form without editing of any field, the first state is stored.
Comments
Comment #1
Micha1111 commentedThere is the same bug with version 6.x-1.0
After editing the node, sid 2 is stored (thats ok)
Comment #2
jvandyk commentedCould you please provide more information? When you edit the workflow that is assigned to that node type, what are the permissions?
Comment #3
Micha1111 commentedI found out, what happens.
Last week, I enabled the module "submitagain".
This module adds a new button "Save and create another" to the node/add-form of a choosen contenttype.
But after pushing this button, only the node is saved without saving the workflow state.
I don't know, in which order the functions of both modules work and I don't know the functions behind the usual button "save".
The combination of modules could be the problem.
If it isn't a problem of workflow, I'll add an issue to the submitagain module.
Your module works fine, if I push the usual button "save".
Thanks in advance !
Comment #4
avpadernoI changed the category as the report doesn't describe a Workflow bug.
Comment #5
jvandyk commentedComment #6
moshe weitzman commentedJust committed a different fix. Actually, it was a fumigation. Module is small and clean now. Release coming in a few mins.