-
Bug
-
Resolution: Fixed
-
Blocker
-
5.5, 5.5.1
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 83
-
5
The versioned nodes are being moved to another location and the path of the current versioned node is /19, while the new path, being calculated from this versioned node uuid, is /19/33/44 (current uuid is like 19xxxx-33xxxx-44xxx-etc). While moving the former under the later we've met JCR consistency restriction, that the source path is an ancestor of destination path.
And also set debug level for the warn messages to prevent flooding the log.
Acceptance criteria
- caused by
-
MAGNOLIA-6774 Same uuids in multiple workspaces leads to corrupted versions
- Closed
- relates to
-
MAGNOLIA-7006 same name siblings issue in MigrateVersionWorkspacesToNewStructureTask and in CopyUtil
- Closed