-
Bug
-
Resolution: Fixed
-
Neutral
-
5.4
-
None
-
5.4 alpha-2 CE and EE bundles
When using the magnolia.resources.dir property in the magnolia.properties file to define a folder outside of ${magnolia.home} the YAML config files are correctly loaded, but the template scripts in the same place create a FileNotFound exception. Even after a restart the template scripts cannot be found. Works again once you place everything in ${magnolia.home} again.
- depends upon
-
MAGNOLIA-6253 Split/Extract FreeMarker support classes out of core
- Closed
- is causing
-
MGNLRES-179 Migrate all resources from templates to resources
- Closed
-
MGNLINTEMPL-79 Deprecate and remove installation tasks for JcrRepoTemplateLoader, since it is now covered by resource API
- Closed
- is depended upon by
-
MAGNOLIA-6248 A sub-directory should be set in magnolia.properties: magnolia.resources.dir
- Closed
- is duplicated by
-
MAGNOLIA-6247 JavaFree Module templatescript cannot be found when magnolia.resources.dir is not Magnolia Home
- Closed
- is related to
-
MAGNOLIA-6106 The yaml configuration source is decoupled from accessing the file system so that the yaml file can be provided from different sources.
- Closed