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

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

      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

        Acceptance criteria

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

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD