Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
5.5.2, 5.5.3
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 95
-
5
Description
As we got move node error due to 'an item with the same name already present' here:
Caused by: javax.jcr.ItemExistsException: The move operation was not completed due to an item with the same name already present. at info.magnolia.jcr.wrapper.MagnoliaSessionWrapper.move(MagnoliaSessionWrapper.java:63) at info.magnolia.jcr.util.NodeUtil.moveNode(NodeUtil.java:523) at info.magnolia.setup.MigrateVersionWorkspacesToNewStructureTask.doExecute(MigrateVersionWorkspacesToNewStructureTask.java:154) at info.magnolia.module.delta.AbstractRepositoryTask.execute(AbstractRepositoryTask.java:57)
Probably MigrateVersionWorkspacesToNewStructureTask.getSavePath(Node) algorithm is not a complete solution to customers who have a large amount of data to migrate.
Same can happen in CopyUtil
javax.jcr.ItemExistsException: The move operation was not completed due to an item with the same name already present.
at info.magnolia.jcr.wrapper.MagnoliaSessionWrapper.move(MagnoliaSessionWrapper.java:63)
at info.magnolia.jcr.util.NodeUtil.moveNode(NodeUtil.java:523)
at info.magnolia.cms.core.version.CopyUtil.moveChildren(CopyUtil.java:391)
at info.magnolia.cms.core.version.CopyUtil.moveChildren(CopyUtil.java:389)
at info.magnolia.cms.core.version.CopyUtil.importNode(CopyUtil.java:378)
at info.magnolia.cms.core.version.CopyUtil.doImport(CopyUtil.java:149)
Checklists
Acceptance criteria
Attachments
Issue Links
- relates to
-
MAGNOLIA-6933 MigrateVersionWorkspacesToNewStructureTask fails in case where moved node has same name as the new generated parent
-
- Closed
-
-
MAGNOLIA-7230 Incorrect task order of MigrateVersionWorkspacesToNewStructureTask
-
- Open
-
- mentioned in
-
Page Loading...