[MGNLSTK-1496] STK has no (Default)I18nContentSupport anymore Created: 27/Jul/15  Updated: 06/Aug/15  Resolved: 05/Aug/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: base system
Affects Version/s: 2.9
Fix Version/s: 2.9.1

Type: Bug Priority: Critical
Reporter: Philip Mundt Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: backlog541
Remaining Estimate: 0d
Time Spent: 4.5h
Original Estimate: Not Specified

Attachments: XML File config.modules.standard-templating-kit.config.site.i18n.xml    
Issue Links:
causality
caused by MGNLSITE-22 Resolve i18nContentSupport from sites... Closed
Template:
Acceptance criteria:
Empty
Sprint: Sprint 4 (Kromeriz)
Story Points: 5

 Description   

In a CE instance STK was relying on the info.magnolia.cms.i18n.DefaultI18nContentSupport defined under config:/server/i18n/content. In MGNLSITE-22 the info.magnolia.module.site.i18n.SiteI18nContentSupport was introduced, which delegates to the i18n content spport defined on site-level – but STK doesn't have one in a CE bundle.

This should be added to /modules/standard-templating-kit/config/site/i18n in order to follow the pattern of one single source of site definition (migration is done by task).

Side-effects

UI tests are failing due to missing i18n content spport. See:

  • info.magnolia.integrationtests.uitest.CompositeFieldUITest.testI18nCompositeField()
  • info.magnolia.integrationtests.uitest.MultiFieldUITest.testI18nMultiField()

Tasks

  • Add default i18n content support definition to STK's site definition
    • Should be enabled=false just like the default used to be
  • Adjust UI tests to be setting the new property under /modules/site/config/site/i18n/enabled
    • info.magnolia.integrationtests.uitest.MultiFieldUITest
    • info.magnolia.integrationtests.uitest.CompositeFieldUITest
    • See: #setUp() and #tearDown()


 Comments   
Comment by Philip Mundt [ 27/Jul/15 ]

Attaching the site's i18n content support, see config.modules.standard-templating-kit.config.site.i18n.xml

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