[MGNLUI-2659] i18n: setting different defaultLocale in site definitions messes up language contexts in website authoring Created: 09/Feb/14  Updated: 04/Nov/14  Resolved: 04/Nov/14

Status: Closed
Project: Magnolia UI
Component/s: dialogs, page editor
Affects Version/s: 5.2.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Petr Kadlec Assignee: Mikaël Geljić
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

If defaultLocale of a site is set to different value than defaultLocale of 'default' definition then language contexts dont work properly in Pages.

Let's say this is the configuration in site definitions:

  • default > locales: en,de; defaultLocale : en; fallbackLocale: en
  • mysite > locales: cs,en,de; defaultLocale : cs (czech), fallbackLocale: cs

..then:

  • pages are always opened in english (defaultLocale of mysite is not respected)
  • dialogs are always opened in english, no matter what language page is actually edited in - it actually works like this everywhere, is this intended behaviour, not to respect current language context and always open dialog in default locale? Seems very confusing for editors.
  • if czech text of an item exists and if page is in english context, czech text is shown instead of english translation, that is also present. German translation is shown fine.

Probably related to MAGNOLIA-3352, which seems to be fixed now - locales from site definitions are now respected, jsut defaultLocale messes things up.



 Comments   
Comment by Mikaël Geljić [ 04/Nov/14 ]

Hi Petr,
We have fixed a series of i18n issues since this one was reported.
Most notably, MGNLUI-2696 and MGNLUI-3128 seem to have addressed the issues you described.
As a result I'll close this ticket; please do reopen it in case there is still an issue or we overlooked something.
Thanks for reporting!

Generated at Mon Feb 12 08:58:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.