Details
-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
Description
When we version we clone the node and its children to mgnlVersions based on rules. We clone paragraphs together with the page but not the subpages. If this rules are not applied consequently then it can happen that a node we are activating/versioning already exists as a subnode of another node and then the process fails.
We had several issues related to the DMS with this but currently again in the Data module (MGNLDATA-124).
Since this nodes are just handles to the version history after we versioned the content, we could simply purge all content of the node after the versioning.
Checklists
Acceptance criteria
Attachments
Issue Links
- is depended upon by
-
MGNLDATA-124 activation of hierarchical data fails
-
- Closed
-