-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Foundation 3, Foundation 4, Foundation 5
-
5
A light module should be able to supply the configuration which is typically stored in the "config" folder directly under a modules configuration in the config app.
For example:
In AdminCentral configuration app:
"/modules/tours/config"
This could possibly be implemented so: the module descriptor can also specify the configuration that is typically supplied by JCR in the /modules/modulename/config node.
Additionally, a 2nd module must be able to decorate this configuration via yaml files that it provides.
- causes
-
MAGNOLIA-7549 Arrays in beans in module configurations are not set properly
- Accepted
- depends upon
-
MAGNOLIA-7432 Draft concept for component configuration in light modules
- Closed
-
MAGNOLIA-7444 Definition app problems in modules configurations
- Closed
- is causing
-
MGNLEESOLR-135 Magnolia 6.1 DataIndexer not initialized
- Closed
-
MAGNOLIA-7636 "Bean Property is Skipped" Error
- Closed
-
MAGNOLIA-7878 Decoration mechanism fails
- Closed
- is depended upon by
-
MGNLUI-4765 Make Find Bar configurable via YAML
- Closed
- is related to
-
MAGNOLIA-7636 "Bean Property is Skipped" Error
- Closed
-
MAGNOLIA-6379 Changing properties of a JCR based definition triggers repopulation of all templates
- Closed
- relates to
-
MAGNOLIA-6532 JCR bootstrap imports without Maven Modules
- Closed