Signals in Public API are executed after operations, so currently the slot for Legacy Content Delete triggers fatal error because it tries to load the object to be able to use eZSearch::removeObject( eZContentObject $object );

However neither ezsolr or ezsearch search engines need anything but content object Id.

So suggested solution:

• Add new method 'removeObjectById' on eZSearch and ezpSearchEngine interface, impl in ezsearch and ezsolr
• deprecate ::removeObject() and make it call the new function instead internally
• Adapt LegacyContentDelete Slot to use new method instead to avoid trying to load object