[MGNLUI-2520] Re-Enable multisite-resolution in PageEditor Created: 12/Dec/13  Updated: 20/Dec/13  Resolved: 18/Dec/13

Status: Closed
Project: Magnolia UI
Component/s: page editor
Affects Version/s: None
Fix Version/s: 5.2.1

Type: Bug Priority: Critical
Reporter: Philip Mundt Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLMODSTR-5 Cannot go to admincentral from domain... Closed
dependency
is depended upon by MULTISITE-10 Implement I18nAuthoringSupport so tha... Closed
relation
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
Release notes required:
Yes

 Description   

Site-resolution in the PageEditor doesn't work. For all pages "default" site will be selected, thus returning wrong I18nContentSupport for sites that might have been specified in MultiSite.

Seems to be related to the AggregationState which is not "aware" of the site anymore, as the PageEditor uses the one from Vaadin backend rather than the one from the page itself.

Symtoms
If a custom site specified in MultiSite (e.g. demo-project) has different i18n settings, these will NOT be properly displayed in the LanguageSelector of the PageEditor if an admin navigates to that "site". Consequently content elements won't be editable in all languages specified.

4.5
In 4.5 the PageEditor used the same AggregationState than the rendered page, thus site resolution would work. This is not the case anymore.


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