DefaultLocale and fallbackLocale dont behave as expected when creating a new Site definition (MGNLEE-200)

[MGNLEE-228] Creation of a new component for Multi language site doesn't behave as expected. Created: 10/May/12  Updated: 24/May/12  Resolved: 11/May/12

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 4.5.2
Fix Version/s: 4.5.3

Type: Sub-task Priority: Major
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-4407 Creation of a new component for Multi... Closed
Template:

 Description   

When creating a new component (TextImage component in an article page) the Dialog always used the default language. If in the Author Instance, I set a language (not the default one. GE in the demo-project) and create a new TextImage component, the content will be stored as default language (no _de for the node property name). If I edit the previously created component, the fields I just defined (Subheading, text) are gone (Now the dialog recognize that he should use GE).



 Comments   
Comment by Eric Hechinger [ 10/May/12 ]

In the class DefaultI18nAuthoringSupport.i18nIze(Dialog dialog)
when a Dialog is related to a new component the following condition return false.
dialog.getStorageNode() != null
This skipped the language setting of the Dialog.

After a discussion with Jan, we agreed to remove this condition.

Comment by Eric Hechinger [ 11/May/12 ]

Git commit.

Generated at Mon Feb 12 05:27:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.