-
Bug
-
Resolution: Duplicate
-
Neutral
-
None
-
None
-
None
-
Empty show more show less
-
UI Maintenance 2
-
5
Steps to reproduce
- Given a stored property foo=en_GB (e.g. from the old UI framework, bootstrap file)
- Try to load this property with new framework
- Use a select field with the datasource named available-locales
- TODO add example config for convenience
Expected results
The value is loaded into the field.
Actual results
TODO
Workaround
Migrate the data (e.g. en_GB to en-GB).
Development notes
- info.magnolia.ui.datasource.locale.LocaleSelectFieldSupport#defaultConverter uses the new java format, LocaleUtils from apache might be able to read both fromats
- available-locales datasource __ is not documented _https://docs.magnolia-cms.com/product-docs/6.2/Apps/App-configuration/Data-source-definition.html_
Acceptance criteria
- clones
-
MAGNOLIA-7897 Provide Compatibility And Documentation for Changing Java 7 Locale Names To Java 8
- Closed
- is cloned by
-
MGNLDEMO-348 Changing Java 7 Locale Names To Java 8 for demo project
- Closed