Details
-
Bug
-
Resolution: Fixed
-
High
-
4.3.0, 4.4.0, 4.5.0, 4.6.0, 4.7.0, 5.0, 5.1, 5.2-beta1
-
None
Description
EZP-19660 introduced begin & commit steps in the publish operation. When the publish operation is interrupted by the pre-publish trigger, the transaction stack is left inconsistent, as the commit step won't be performed.
Several bugfixes were made where the operation was used, but it should actually be fixed in the trigger code:
the DB transaction stack should be identical before and after eZOperationHandler::execute( 'content', 'publish' ) is called.
Attachments
Issue Links
- discovered while testing
-
EZP-19660 viewcache is cleared/refreshed before content publish operation is finished
- Closed
- relates to
-
EZP-22782 eZWorkflowType::STATUS_REDIRECT sets bad object version status
- Closed
-
EZP-23231 "Wait until date" content not showing on Dashboard/My pending items
- Closed
-
EZP-19077 fatal error in ezjscore when encoding an object without a node
- Closed
-
EZP-20558 Workflow Event/Approve not working correctly
- Closed
-
EZP-21563 workflows: adding approval to media tree causes fatal error
- Closed
- links to