Problem with collaboration cronjobs

Monday 06 September 2010 1:34:08 am

I set up an installation of Exponential 4.3 with a workflow to approve user registration.

To do this I configure a crontab, but if my admin user doesn't approve Item and delete it the cronjobs goes to crash with this message:

Fatal error: Call to a member function contentAttribute() on a non-object in /var/www/vhosts/technolift.com/httpdocs/kernel/classes/collaborationhandlers/ezapprove/ezapprovecollaborationhandler.php on line 107

I solved this problem patching ezapprovecollaborationhandler.php by inserting a control on static function contentObjectVersion( $collaborationItem ) :

from this:
static function contentObjectVersion( $collaborationItem ) {
$contentObjectID = $collaborationItem->contentAttribute( 'content_object_id' ); $contentObjectVersion = $collaborationItem->contentAttribute( 'content_object_version' );
return eZContentObjectVersion::fetchVersion( $contentObjectVersion, $contentObjectID );
}

to:

static function contentObjectVersion( $collaborationItem ) {
if(!empty($collaborationItem)) {
$contentObjectID = $collaborationItem->contentAttribute( 'content_object_id' ); $contentObjectVersion = $collaborationItem->contentAttribute( 'content_object_version' );
return eZContentObjectVersion::fetchVersion( $contentObjectVersion, $contentObjectID );
}
}

I'm sorry for my english...
Bye
Michele

Tuesday 07 September 2010 1:09:04 am

The same thing that I ask to my customer.
i don't know how, but I found it deleted and crontab send me a lot of email with the classic message "Exponential get abrutly ended....", so comparing ezuser table with ezcontentobject and ez collaborationitem tables i found that an item in ezuser table was missed.

Michele

Tuesday 07 September 2010 5:33:22 am

Sure my customer cannot delete parent node.

i need more time to investigate.
Thank you a lot Chen.

Bye