-
Improvement
-
Resolution: Fixed
-
Blocker
-
3.0.0
In 6.3, sites were upgrade to a conventional definition registry.
The site definitions are thus loaded in YAML from light-modules, under <module-name>/sites path (see here).
To ensure a smooth upgrade from 6.2, let's add backward-compatibility loading sites from the previous multisite location in JCR, under multisite/config/sites as it was until 6.2.
Previous description
via oanh.thai
Create ready-to-use fallback site (programmatically) if there is no available site
Complementarily, in 6.3 dx-core-webapp without installing demo-travel module that includes fallback site. So there is no way to use page-editor app without fallback site.
Ex: See more problem reported in when using dx-core-test-webapp.
https://magnolia-cms.slack.com/archives/C02RSFYAH6D/p1701229569335609
In docu: we already mention that fallback is needed for multi site. See https://docs.magnolia-cms.com/product-docs/6.2/developing/templating/site-definition/how-to-use-multisite/fallback-site/#_choosing_a_fallback_site_definition
Propose fallback yaml
- is superseded by
-
-
- Accepted
-
- relates to
-
MULTISITE-193 Site configuration changes in YAML files aren't reflected at runtime
-
- Closed
-
-
-
- Closed
-
-
MGNLEE-852 Remove site configuration fallback.yaml from ee-test
-
- Closed
-
