Details
-
Bug
-
Resolution: Fixed
-
High
-
1.3.2, 1.4.2
-
None
Description
When a user who has created content is deleted then the created content is broken as the system still tries to load the already deleted user object.
Steps to reproduce:
- Open the backend and create a new user "usr-001".
- Login with "usr-001" and create a new article "Article #001".
- Logout from "usr-001" and delete it with another account.
- Try to edit "Article #001".
- When "Article #001" is loaded, you will get the following error message:
Could not load the user with id '/api/ezp/v2/user/users/52'
Expected behaviour:
- Non existent users should not prevent content from being loaded, displayed and edited.
Stack trace
"ErrorMessage": { "_media-type": "application/vnd.ez.api.ErrorMessage+json", "errorCode": 404, "errorMessage": "Not Found", "errorDescription": "Could not find 'Content' with identifier'array ( 'id' => '52', 'languages'=> NULL, 'versionNo' => NULL)'", "trace": "#0 vendor/ezsystems/ezpublish-kernel/eZ/Publish/Core/Repository/UserService.php(514):eZ\\Publish\\Core\\Repository\\ContentService->internalLoadContent('52') #1 vendor/ezsystems/ezpublish-kernel/eZ/Publish/Core/SignalSlot/UserService.php(242): eZ\\Publish\\Core\\Repository\\UserService->loadUser('52') #2 app/cache/dev/appDevDebugProjectContainer.php(41365): eZ\\Publish\\Core\\SignalSlot\\UserService->loadUser('52') #3 vendor/ezsystems/ezpublish-kernel/eZ/Publish/Core/REST/Server/Controller/User.php(179)" }
Attachments
Issue Links
- is duplicated by
-
EZP-26377 UI issues when user does not have access to author/relation/locations
- Closed
- relates to
-
EZP-26377 UI issues when user does not have access to author/relation/locations
- Closed
-
EZP-26366 Prevent users to be deleted if they have existing content to prevent errors
- Closed
-
EZEE-977 Prevent users to be deleted if they have existing content to prevent errors
- Confirmed
- testing discovered
-
EZP-26475 Infinite loader if embed Content item is unreachable
- Closed