Note: This has popped up when using a custom UserService, subclassing eZ\Publish\Core\Repository\UserService.

• method updateUser calls $this->loadUser()
• which calls $this->repository->getContentService()->internalLoadContent( $userId );
• but this method is not in PAPI classes
• it is also not implemented by SignalSlot\ContentService

so if our own UserService gets injected an instance of SignalSlot\ContentService, it will not be able to update user passwords.

Quick workaround: cleanup the SignalSlot\ContentService class, remove all non-wrapped methods and add a magic __call() which forwards all other methods to $this->service

Better workaround: have Core\UserService never depend on non-papi methods of ContentService