#011577: workflow cancelled when reediting the draft of a previously rejected content

Description:

If I have multiplexed workflows, when a content is rejected in a multiplexed workflow, when I edit the draft to correct it, when publishing, I get an empty grey page with the text "Content publish cancelled"

It has been observed on 3.8.4, 3.8.6, 3.9.2 and 3.10.0


Environment:

Operating System: Linux Debian sarge
PHP Version: (please be specific, like '4.4.4')
Database and version: Mysql 4.1.11
Browser (and version):


Steps to Reproduce:
  • make a plain site installation of eZ
  • log as admin
  • create a user in the Editor user group
  • add the "collaboration/access to all function" to the policies for the Editors
  • create a workflow "test wf standard" with a single approve event whose approver is the created editor, and that will apply to the standard section.
  • create a workflow "test wf media" with a single approve event whose approver is the created editor, and that will apply to the media section.
  • create a workflow "test wf multiplexer" with 2 multiplexer event: the first is triggers "tst wf media" on the media section, the second triggers "test wf standard" for the standard section
  • set your before publish trigger to "test wf multiplexer"
  • create an article in the standard section and publish it
  • run the workflow cronjob (optional)
  • log as the editor to approve the article
  • Deny the approbation
  • run the workflow cronjob
  • log as admin
  • go to the "My account" tab and edit the draft of the rejected article
  • publish it

- Attachments

No attachments for this issue.


- Comments

Ooops, I've forgotten some details:

  • when you click on the "back" button of the browser, and send it again for publishing, it's OK
  • after further investigations, it seems to me that the pb is in eZModuleOperationInfo::execute, around dealing with memento data (line 176 to 182 in the 3.8.6 code)
#254019 by Eric Bourgain on October 5th, 2007 [Permanent Link]

No the problem was in the multiplexer event..
Here is the patch for this issue I will apply it to all branches after we test it a bit more..

#255229 by Sergiy Pushchin on December 21st, 2007 [Permanent Link]
- Attachments: » multiplexer_deny310.patch

I have the same bug on 4.0.1.
I have just transform multiplexer_deny310.patch for ez 4 and it's work properly.

#261829 by DEHESTRU Benoît on June 3rd, 2009 [Permanent Link]
- Attachments: » ezmultiplexertype.patch (Patch for ez 4.0.1)

Same in 4.1.3 (4.1.x)

Thank you very much for your patch.

#264344 by Matthieu MORATILLE on January 19th, 2010 [Permanent Link]

Same in 4.0.3...
Thanks a lot for your patch !

#263688 by Pierre Martel on October 29th, 2009 [Permanent Link]

Why it's not resolved in new versions ????

#264605 by Pierre Martel on February 11th, 2010 [Permanent Link]

Was the patch proposed a bit above applied to master ?
I could note the samekind of behaviour on projects.ez.no (4.0.1). This is damaging any editorial chain relying on our workflows.

Cheers !

#268418 by Nicolas Pastorino on November 29th, 2010 [Permanent Link]

The reason for this not being in master is that it needs a lot of testing.
As far as I can see only people who have issues with this have so far confirmed the patch, but we also need people that use the workflow system differently to test it to make sure it does not cause regressions..

#269341 by André R. on March 4th, 2011 [Permanent Link]

I can confirm this same bug on 4.5.0... amazing that is still unresolved seems that nobody out there is using approval workflow :(

#272704 by Xavier Serna on November 17th, 2011 [Permanent Link]

- History
Properties
Type Bug
Priority Medium
Component Workflows
Affects 3.10.0
Fix Version 4.5.0alpha - Matterhorn alpha
Reporter Eric Bourgain
Responsible -
Status 0 New
Resolution UNRESOLVED
Created October 5th, 2007
Updated November 17th, 2011
Resolved -
 
Navigation [Permanent Link]
Previous Issue
Back to Issues List
Next Issue: #019127
  DB Deadlocks on ezcontentobject_tree when updating subnode