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

Micha1111’s picture

There is the same bug with version 6.x-1.0
After editing the node, sid 2 is stored (thats ok)

jvandyk’s picture

Status: Active » Postponed (maintainer needs more info)

Could you please provide more information? When you edit the workflow that is assigned to that node type, what are the permissions?

Micha1111’s picture

I 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 !

avpaderno’s picture

Title: no state stored in database after adding a new node » No state stored in database after adding a new node
Category: bug » support
Status: Postponed (maintainer needs more info) » Active

I changed the category as the report doesn't describe a Workflow bug.

jvandyk’s picture

Project: Workflow » Submit Again
Version: 6.x-1.x-dev » 6.x-1.1
moshe weitzman’s picture

Status: Active » Fixed

Just committed a different fix. Actually, it was a fumigation. Module is small and clean now. Release coming in a few mins.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.