Skip to content
Browse files

fix bug in 'co delete', go with the default co delete behaviour which…

… removes the subtree, too
  • Loading branch information...
ReaderBound Dev
ReaderBound Dev committed Feb 12, 2019
1 parent 1be0eed commit 5d5d6a445d0caded465346483e949f243a420bfb
Showing with 3 additions and 1 deletion.
  1. +3 −1 modules/contentobject/index.php
@@ -317,7 +317,9 @@ private function delete( $objectId )
$adminUserObject = eZUser::fetch( eepSetting::PrivilegedAccountId );
$result = eZContentObjectOperations::remove( $objectId, false ); // false to indicate, 'dont bother removing subtrees, just purge() it'
// the default behaviour is to delete the subtree,
// FYI, purge(), the non-default behaviour, leaves all the children in place, but up 1 level, and does not update their node-paths ... that is, it corrupts the content structure
$result = eZContentObjectOperations::remove( $objectId );
if( $result )

0 comments on commit 5d5d6a4

Please sign in to comment.
You can’t perform that action at this time.