Details
-
Improvement
-
Resolution: Fixed
-
Major
-
1.0.4
-
None
Description
Suppose you use the Content importer with complex/deep folder structures and export these into several files. In that case, errors occur during the import because the import order is the wrong way around, and therefore, sometimes the required path still needs to be created. Especially when importing test data for repeatable tests, this is necessary.
Steps to reproduce:
Take any content app and create the following folder structure:
- Level1 (folder)
- Level2 (folder)
- Item1 (node)
- Item2 (node)
You can observe the behavior if you export Item, Item2, and the folders individually and put them into the content importer.
Actual result:
The content importer always takes the deepest/longest path first.
Expected result:
The content importer should always process the shortest path first.
We have this requirement both in our internal demo team and specifically from two customers.
Checklists
Attachments
Issue Links
- split to
-
MGNLCI-32 Create 6.3 compatible version of content importer
-
- Accepted
-