Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6151

BootstrapUtil / DataTransporter creates hierarchy using mgnl:content which might not always be the correct nodeType

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 5.3.7
    • None
    • None

    Description

      When bootstrapping content, where (some) parent folders do not exist (hierarchy is determined from bootstrap filename), info.magnolia.importexport.BootstrapUtil will always use NodeTypes.Content.NAME as node type which might not always be the correct type and also lead to problems when activating content (when the resulting hierarchy is of mgnl:content > mgnl:contentNode > mgnl:content).

      This is especially a problem for repositories with custom node types such as dam, where folders will be create with the default node type mgnl:content but should rather be mgnl:folder. As a result those nodes/assets will not appear in the DAM App.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              pmundt Philip Mundt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD