[MGNLSITE-22] Resolve i18nContentSupport from sites configuration Created: 16/Jul/15  Updated: 15/Sep/15  Resolved: 20/Jul/15

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

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.75d
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-31 SiteI18nContentSupport fails with NPE... Closed
relates to MGNLDEMO-88 Remove i18nContentSupport bootstrap f... Closed
relates to MULTISITE-49 Adapt to changes in site and i18nCont... Closed
causality
is causing MGNLSTK-1496 STK has no (Default)I18nContentSuppor... Closed
dependency
is depended upon by MAGNOLIA-6316 Provide templating functions to i18ni... Closed
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)
Sprint: Sprint 2 (Basel)
Story Points: 1

 Description   

To get the i18nContentSupport for the current site you have to get it manually from the Site instead of just injecting it where needed. There seems to be a delegating implementation for MultiSite, but that is not installed into /server/i18n/content and has no dependency to multisite.

Moving the implementation to site and make sure it gets installed.


Generated at Mon Feb 12 07:11:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.