-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
DevX 12, DevX 13, DevX 14
-
8
As a developer, I would like to have a registry for sites, rather than working in the configuration of the site or multisite module, so that sites work consistantly with other key Magnolia entities (dialogs, contenttuypes, apps) for example being displayed in the Definitions app.
Thanks to https://jira.magnolia-cms.com/browse/MAGNOLIA-6521Â it is now possible to configure Sites via YAML files. However one does it by decorating the "config" of the multisite module instead of supplying definitions in the normal ways.
This makes site configurations hard to understand and debug, as the full "resolved" definition is not shown in the Definitions app. Some issues:
- It can be hard to know what the actual final definition is.
- Problems may not be reported.
- Decorations are not reported and displayed in the definitions app.
- is causing
-
MGNLUI-8766 Locale selector doesn't reflect changes in site i18n setting
- Closed
- is related to
-
MULTISITE-191 Page editor doesn't resolve correctly site and fallbacks to "fallback" one
- Closed
- relates to
-
MULTISITE-193 Site configuration changes in YAML files aren't reflected at runtime
- Closed
-
CFGUI-157 Display site registry in Definitions app
- Closed
-
MGNLDEMO-396 Migrate site definitions from jcr to yaml
- Closed
-
MULTISITE-122 As a developer, i want to be able to configure sites via yaml, so i can have different configurations for different SPAs
- Closed
-
MULTISITE-133 New MultiSiteRegistry doesn't limit number of sites according to allowed sites by the license
- Closed
- supersedes
-
MGNLSITE-29 Sites via YAML
- Closed
- mentioned in
-
Page Loading...
1.
|
Implementation | Completed | Milan Divilek | |||||||||
2.
|
Review | Completed | Jaroslav Simak | |||||||||
3.
|
piQA | Completed | Jaroslav Simak | |||||||||
4.
|
QA | Completed | Oanh Thai Hoang |
|
||||||||
5.
|
Fix error on ui test | Completed | Milan Divilek |