Uploaded image for project: 'Content Importer'
  1. Content Importer
  2. MGNLCI-11

The import directory shouldn't have to be a subdirectory of the resources directory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • 1.0
    • None
    • None
    • Basel 63
    • 1

    Description

      Currently the importer only works if the dir specified with magnolia.content.bootstrap.dir is the same as magnolia.resources.dir, or a subdirectory of it.

      Conceptually this is strange for a developer, since the magnolia.resources.dir is known as the location that holds the light modules. It should be possible to specify any directory in magnolia.content.bootstrap.dir

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                ilgun Ilgun Ilgun
                czimmermann Christopher Zimmermann
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD