Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
4.6.0
-
None
-
Operating System: Debian GNU/Linux 6.0
PHP Version: 5.3.3-7+squeeze8
Database and version: 5.1.49-3
Description
Hi there,
We got a fatal error when running workflow.php cron :
Call function remove() on a non object line 51 ($bodyMemento->remove())
The WF event deferred to cron is quite simple, it runs before content / publish, just returns status deferred to cron at first execution, then returns status rejected or cancelled (error occurs on both).
Had a look and some debug in kernel and lib, found that eZModuleOperationInfo creates bad links between eZOperationMemento and eZWorkflowProcess
Two mementos are created, one main's field is set to 1, the other is set to 0.
The one linked to the WF process by memento_key isn't main.
I used an eZModuleOperationInfo class from an eZ 4.4, everything ran without any problem
Regards,
Team Internethic.
Steps to reproduce
- add a Workflow before content / publish with at least one event which returns eZWorkflowType::STATUS_DEFERRED_TO_CRON_REPEAT, and which returns eZWorkflowType::STATUS_REJECTED when ran by workflows cron
- run workflow.php
Used eZModuleOperationInfo class in 1st attachment
Used WF Event in 2nd attachment