|
Andre Felipe Machado
|
Monday 31 October 2005 12:16:39 pm
Hello,
when tried to run cronjob Fatal error: Call to a member function on a non-object in /kernel/classes/workflowtypes/event/ezapprove/ezapprovetype.php on line 155
Fatal error: eZ publish did not finish its request
The execution of eZ publish was abruptly ended, the debug output is present below.
And no further output
Please, what can I do?
Regards.
Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
http://www.techforce.com.br
|
|
Andre Felipe Machado
|
Tuesday 01 November 2005 2:45:04 am
Hello,
Remembering the steps that lead to the error:
I cleaned the trash folder.
Well, restored from a database backup made before the trash cleaning (using the empty trash button).
The error gone.
So, there is something broken at the trash...
Regards.
Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
http://www.techforce.com.br
|
|
Andre Felipe Machado
|
Wednesday 02 November 2005 4:44:06 am
Hello,
By selectively removing objects from trash, I isolated 2 articles that did not have main location for publishing. (these tries involved some database restore operations...)
One of them I edited and assigned a location and was able to delete and remove it.
The last object, despite being assigned one mail publish location, did not come to a consistent state.
If I removed it from trash, the cronjob workflow crashed.
So, as a workaround I restored db backup and assigned it an invisible draft folder location. It is still there, but invisible....
Now the cronjob can run without crash.
but the object is broken, inconsistent, and I do not know how to repair it in order to remove it.
How an object could become broken?
Why the system does not dectect it? (at the admin interface, the verify upgrade is ok)
Regards.
Andre Felipe
---
A Debian user never dies. Issues a last command:
shutdown -h now
http://www.techforce.com.br
|
