Issue Type: Bug Bug
Affects Versions: 5.3.2
Assignee: Unassigned
Attachments: fallbackLocal.jpg
Components: dialogs, page editor
Created: 28/Aug/14 11:00 PM
Description:

This issue is very related to MULTISITE-22, it's is follow up.
The described behavior was also detected on the defaultLocale (MULTISITE-22).

Description:
When changing in a specific site definition the defaultLocale & the fallbackLocale, the already stored content should appear in a dialog.
This is not the case because the fallbackLocale is still served from the "default" site definition, see print screen fallbackLocal.jpg.
(MULTISITE-22) corrected that the defaultLocale is set correctly and the dialog opens in the default locale (in this case "de") from the specific site definition, but because the fallbackLocale(en) != defaultLocale(de) the dialog still want to edit a property with "_en" appended to its name. There fore the dialog is empty, and if entering content it will store a "%propertyName_fallsbackLocale%" property.

Reason:
In info.magnolia.ui.framework.i18n.DefaultI18NAuthoringSupport.i18nize(HasComponents, Locale) the locale provided as the parameter is the correct defaultLocal. But in this code:

boolean isFallbackLanguage = i18nContentSupport.getFallbackLocale().equals(locale);

The provided fallbackLocal from i18nContentSupport (Object=MultiSiteI18nAuthoringSupport) is from the "default" site definition (set in MultiSiteFilter). This because the detected site definition in the scope of the pages app is not the actual specific site definition from the edited page (different requests). (same problem as in MULTISITE-22)


Tried solution:
I tried to create also a node dependent getFallbackLocale(Node node) method for MultiSiteI18nAuthoringSupport & DefaultI18nAuthoringSupport as done in the MULTISITE-22 for the defaultLocale.
The problem is that in the calling class of the method DefaultI18NAuthoringSupport#i18nize is the dialogs view:
info.magnolia.ui.dialog.formdialog.ItemFormView.createLocaleSelector()
I haven't found a way to retrieve the content the DialogView operates on.
Which could be well intended by the MVP pattern. A different solution might has to be found.

Project: Magnolia UI
Labels: support
Priority: Major Major
Reporter: Christian Ringele
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to