[MULTISITE-22] Edit mode locale selector is not populated outside non-default site definition Created: 09/Jul/14  Updated: 18/Aug/15  Resolved: 24/Jul/14

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: 1.0.4
Fix Version/s: 1.0.5, 1.1.1

Type: Bug Priority: Critical
Reporter: OLD Chris Jennings Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.modules.multisite.config.sites.demo-project-bil.xml     XML File config.modules.multisite.config.sites.test.xml    
Issue Links:
Cloners
dependency
depends upon MGNLUI-3067 Provide method to get the default loc... Closed
is depended upon by MULTISITE-27 Drop-down list of authoring languages... Closed
relation
is related to MGNLEE-200 DefaultLocale and fallbackLocale dont... Closed
supersession
is superseded by MGNLUI-3128 FormBuilder: defaultLocale in dialogs... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by OLD Chris Jennings [ 14/Jul/14 ]

Moved to support as requested by Gokhan Mermer.

Comment by Natascha Desmarais [ 15/Jul/14 ]

Attached a simple test site definition from 5.3.1 bundle with the same symptoms.

Comment by Natascha Desmarais [ 15/Jul/14 ]

Might be related to MGNLEE-200, I remembered we had a similar issue back then about other fallback languages not being picked up other than in the default site def.

Comment by Mikaël Geljić [ 17/Jul/14 ]
  • when site is resolved, do check whether i18n is enabled for it (same as in #getAvailableLocales)
  • also adjust dependency in module descriptor
Generated at Mon Feb 12 06:05:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.