Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.2.26
-
None
-
None
Description
Steps to reproduce
- create workspace "downloads"
- add new asset to workspace
- update asset to create a version
- migrate asset do "dam" workspace
- delete workspace "downloads"
- try to delete migrated asset

Expected results
Asset and its versions get deleted. If a version with a reference to an non existing workspace exists an error is logged but the deletion still works.
Actual results
Asset can not be deleted and an error is thrown that lists the none existing workspace.
Workaround
Groovy Script that deletes the asset without failing.
Development notes
Error is thrown in BaseVersionManager.java:573 because Magnolia tries to get a session for a sourceWorkspace that does not exist anymore.
Either check if the sourceWorkspace still exists with the RepositoryManager or catch the NoSuchWorkspaceException and print the error to the log while removing the version.
Checklists
Acceptance criteria