Closed (fixed)
Project:
Workflow
Version:
6.x-1.0-rc3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Oct 2008 at 22:38 UTC
Updated:
13 Jan 2009 at 03:50 UTC
This is a bug fix and a feature change request rolled into one.
The current workflow_execute_transition() function does not accept a $force parameter although it is used inside the function (and sent by at least workflow_select_given_state_action). Just adding the parameter and defaulting it to NULL does the job.
The feature change request is to allow the workflow to go to the new state even if there is no transition for it, when $force = TRUE. This will allow workflow admins to manually adjust workflows when something goes wrong.
The attached patch accomplishes those two things. Thanks for your consideration.
| Comment | File | Size | Author |
|---|---|---|---|
| kr-force.patch | 943 bytes | infojunkie |
Comments
Comment #1
Balefire commentedSubscribe and +1
Comment #2
verikami commented+2 :-)
...I was just looking for this option, trying to change workflow state between two workflow sets
when using views bulk operations I had msg. that the row was processed, but nothing really happens...
now it works :-)))
Comment #3
jvandyk commentedCommitted; will appear in the next release after RC4. Thanks!