-
Bug
-
Resolution: Fixed
-
Critical
-
1.0.4
When opening a page in a site that uses a non-default site definition with multiple locales:
- The locale selector menu is not initially populated with the current locale.
- On opening the page properties dialog, no locale is selected.
- On adding a new component, no locale is selected.
This leaves the editor with no idea what locale they are working in.
Example site definition attached was created in a freshly downloaded 5.2.5 webapp. Import site definition and create a new STK Home page at /demo-project-bil to reproduce above.
- depends upon
-
MGNLUI-3067 Provide method to get the default locale for a specific node in I18NAuthoringSupport
- Closed
- is depended upon by
-
MULTISITE-27 Drop-down list of authoring languages is not populated with country string
- Closed
- is related to
-
MGNLEE-200 DefaultLocale and fallbackLocale dont behave as expected when creating a new Site definition
- Closed
- is superseded by
-
MGNLUI-3128 FormBuilder: defaultLocale in dialogs is always taken from the "default" site definiton
- Closed
- mentioned in
-
Page Loading...