Closed (fixed)
Project:
Workflow
Version:
7.x-2.0-beta7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Jul 2011 at 07:01 UTC
Updated:
7 Jan 2014 at 16:40 UTC
Jump to comment: Most recent
When changing the state of a node, and adding a comment to that state change in the comment box provided by Workflow, the state is updated twice. For example I move a node from state "Needs Revision" to state "Staged for Publishing", and I leave a comment of "stage it.".
You can see this in the history log on the Workflow tab for the node. First the node changes from "Needs Revision" to "Staged for Publishing", then it "changes" states again from "Staged for Publishing" to "Staged for Publishing".
This doesn't happen if you don't leave a comment.
I'll attach a screenshot.
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot.png | 105.58 KB | jrstmartin |
Comments
Comment #1
jrstmartin commentedI downgraded because of this but it actually happens on 6.x-1.5 as well. Not sure if it's me. Anyone else having this issue? I always made sure to pm-uninstall, cc all, and updb.
Comment #2
jrstmartin commentedThis seems to be the same problem as #472966: Avoid execute_transition twice (when using Rules, Actions). When I disable my rule (Rules module) that performs an action on the node in response to the state change, problem goes away. :/
Comment #3
jrstmartin commentedMore on this and a very hackish patch is available here: Implement subsequent runs control.
Comment #6
Bastlynn commentedDropped down to 6.x-1.5 based on report it happens there too.
Comment #7
johnvD6 version is unmaintained right now. Let's move this issue to #472966: Avoid execute_transition twice (when using Rules, Actions)
Comment #8
johnvWell, this still is a problem. It happens when you activate Rules.
[EDIT: it happens without Rules, too.]
Comment #9
johnvThis is fixed with this commit.