Hey folks,

i got one big problem and i hope you can help me out of this:

Everytime when iam editing and saving a node the Workflow-State is changing the state.
The state is the one which is assigned after a node-creation.

Iam not using rules for workflow transitions.
Can anybody help me out?

Greetings :-)

Comments

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented
Title: Unexpected Workflow state change afterm Node-Edit » Unexpected Workflow state change after Node-Edit
Status: Active » Postponed (maintainer needs more info)

Please upgrade to version 2.4 or -dev. It contains numerous bugfixes.

There is no support for 1.2 anymore.

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

Thanks for your reply...but i cannot upgrade yet.
iam using some modules like "extensions" etc. that are not working with v2.x.

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

I understand. Which are those modules? Perhaps I can patch them.

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

Hi John, that would be great!

Iam using the following Workflow-Modules:

- Workflow 1.2
- Workflow extensions 1.0+3 dev

Thank you very much!!!

Many greetings

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

Workflow extensions is now completely incorporated in version 2.x
just upgrade, disable extensions and test the result. See also the project page.

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

How should i upgrade? Iam using D7.
Should i disable the Workflow Modules before i upgrade?

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

Never did an upgrade before? Remove the old files and replace with the new files. Then goto page update.php. Then(or first) disable workflow_extensions. Normally you would have a test environment, using git or svn, so you can do this on the production site with short downtime.

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

Sure i did it before, but i want to be safe in this way and just asked ;-).
I will do it now!
Thank you very much for your support, john!

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

Good luck. Please share your results script, so others can benefit.

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

Hi john,

i upgraded from 1.2 to 2.4.
Everything seems okay so far... BUT...now i got one big problem.
Every rules with "Set workflow state to..." is not working anymore.

What can it be?

I have to delete "Set workflow state to" in the rules, otherwise the complete rule is not executing anymore.

Any help would be great.

Thank you very much.

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

hey johnv,

i fixed that issue with help of this patch in #9:
https://www.drupal.org/node/2304365

Maybe you can confirm that.

thank you.

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

OK, thanks.
That means, if you upgrade to the -dev version or version 7.x-2.5-beta1, the error should not appear at all. Correct?

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented
Title: Unexpected Workflow state change after Node-Edit » Unexpected Workflow state change after Node-Edit in 7.x-1.2
Status: Postponed (maintainer needs more info) » Active
johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

Oh, if you have any additional tips regarding your upgrade, please add them here: #2352293: Add Migrate support for WorkflowNode data to WorkflowField

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

After recent observations in this case i can say that "Set a workflow state"-Rule doese not working properly!
In the workflow-log the state was changed...but the "real" state doesnt change.

Also the previous-state and the current-state are everytime the same, after an state action.
I have to change by hand from one state back again to target state.

I dont know what is wrong after the upgrade :-(.

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

OK, I'll check this. Which version have you downloaded? I remember have fixed things in this area. According to #2344431: Action "Set Workflow Field" state does not always update the Workflow Field value, you should be using latest dev or workflow 7.x-2.5-beta1.

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

#2189761: How to use Rules support for Workflow Field

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

hi johnv i will now check the 2.5-beta1.
I will give you a report after recent checks.

Thanks for your support!

Update #1 (2.5-beta1):
After creating a new node:
- Error-Message on Website: "Workflow 0 cannot be loaded. Contact your system administrator."
- Message in db-log: "Setting a non-relevant Entity from state 0 to 0"

Nodes have no "Workflow-State" at all (no workflow attached).
No Workflow-Registertab is shown at node-view.

After Edit -> Save Node the node gets a Workflow-State.

Update #2 (latest Dev):
Beginning Tests using latest DEV 2.x:
- Running update.php throws the following messages out (many times):
"Notice: Undefined index: group in workflow_actions_trigger_info() (Line 162 of /var/www/sites/all/modules/workflow/workflow_actions/workflow_actions.module)."
- The Website performance is significant slower. DB-Log many notice messages "Undefined index: group in workflow_actions_trigger_info".

After creating a new node:
- Workflow is set correct.

  • johnv committed 5ba3775 on 7.x-2.x 
    Issue #2369435: Fixed Notice: Undefined index: group in...
johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

Fixed the messages in version 7.x-2.x of workflow_actions_trigger_info() here.

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented
Status: Active » Closed (outdated)

New features for D7 are not processed anymore, (unless a patch is provided)