[MULTISITE-10] Implement I18nAuthoringSupport so that we can get available locales for a node Created: 17/Dec/13  Updated: 19/Dec/13  Resolved: 18/Dec/13

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: 1.0.2

Type: Task Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-2520 Re-Enable multisite-resolution in Pag... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

When editing a page or opening a component dialog, we need to know what are the available locales for this page/area/component node.

Since this is happening in Vaadin UIDL requests, we can no longer rely on aggregation state that is populated by MultiSiteFilter when rendering a page.

It was decided to introduce a getAvailableLocales(Node) method on i18nAuthoringSupport interface; multisite module should now implement it and update configuration so that i18nContentSupport is resolved according to site definitions.

SiteManager already has a utility method: getAssignedSite(Node).



 Comments   
Comment by Mikaël Geljić [ 18/Dec/13 ]

There was an original work-in-progress commit that was partially reverted (MultiSiteI18nContentSupport) by commit 0a1e0c33d854fa7c4d82ddba9067557f59bed7b2.
https://git.magnolia-cms.com/gitweb/?p=enterprise/multisite.git;a=commit;h=f763373c76b139f644d9e4da71ac09da6038c1ec

Will be squashed before merging to master.

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