As a Marketer I want the fragment configuration of OOTB fragments to be localizable when it makes sense

• Type: Story
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Fragment Administration
• Labels:
  • Consider_For_7.4

NEED TO BE RE-THOUGHT:  

Intro/Context:

We introduced the possibility to localize the values of the fragment configuration using "localizable:true" config setting. This option has to be set by a developer to selected fragment config. Liferay OOTB fragments are not localizable by default.

The goal is to make all general fragment configurations localizable by default.

 

Given a Page Creator uses an OOTB fragment and uses a config value for a fragment for a particular language

-

When a page creator change language and changes the configuration for this page

Then the configuration is kept for this language and the Page Creator knows it because a feedback visual is showing that.

-

When a page creator change language of the default language

Then the configuration is changed for all languages but not for the fragments that have localized configurations

-