Details
-
Bug
-
Resolution: Fixed
-
Critical
-
3.0.1
-
None
Description
In ModuleUtil.bootstrap(), we try to create the parent of to-be-imported nodes before delegating to the actual import code (DataTransporter.importXmlStream), but
1- this is always done in the "config" repository (same bug as MAGNOLIA-1326)
2- not visible since done in the system session, which happens to be never same afterwards in most cases *
this is useless since DataTransporter.importXmlStream does it (and in the correct repository this time!)
- It only becomes visible if by chance, after bootstrapping nodes outside the config repository, another module bootstrap files again in the config repository, and thus saves it.
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
MAGNOLIA-1326 ModuleUtil.bootstrap() could accidentally delete nodes in the Config workspace
-
- Closed
-