-
Bug
-
Resolution: Fixed
-
Neutral
-
2.2.19
-
None
-
Empty show more show less
-
DevX 41, DevX 42
-
3
-
Yes
Currently, there are two different approaches for handling locale tags being used in Magnolia. One, takes into account the JVM default locales or the tag is well-formed, but on REST requests, the handling only checks against the default locales, not allowing the usage of other locales like en_TH or en_TW.
This could be adapted to make use of the isLocaleValid class on all cases to allow more flexible usages of locales.
Filter in use for the Delivery Endpoint: https://git.magnolia-cms.com/projects/MODULES/repos/rest/browse/magnolia-rest-jcr-delivery/src/main/java/info/magnolia/rest/delivery/jcr/i18n/I18nContainerRequestFilter.java#126
Behaviour to mimic: https://git.magnolia-cms.com/projects/PLATFORM/repos/main/browse/magnolia-core/src/main/java/info/magnolia/cms/i18n/AbstractI18nContentSupport.java#163
- relates to
-
MAGNOLIA-8229 Non JVM-default Locales are not used in I18n
- Closed
1.
|
Implement | Completed | Valeria Robles-Garzon | |
2.
|
Review | Completed | Rishab Dhar | |
3.
|
Pre-Integration QA | Completed | Rishab Dhar | |
4.
|
QA | Completed | Robert Šiška |