Contexthub Issues on AEM 6.4 (Style System and i18n) | Community
Skip to main content
N
nadeensalvador
March 5, 2020
Solved

Contexthub Issues on AEM 6.4 (Style System and i18n)

  • March 5, 2020
  • 1 reply
  • 4016 views

Hi Experts,

We are using Contexthub on AEM 6.4. Found that when authoring a targeted component for each segment, the style that was selected from the style system is not carried over to the segment-specific version - it only shows on "default". The style system option is also not there when in "Targeting" mode so there is no way to set the style for each segment. Aside from this, the i18n can only be seen on the "default" segment/experiences. For other segments, it always shows the English labels.

 

Has anybody encountered this behavior? Any help, insights, or suggestions are all welcome. Thanks in advance.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vish.dhaliwal

Hello,

It is not possible to use the style system in the targeting mode. An alternate way to achieve that can be by creating the Experience Fragments [1] with different style options and then target using those Experience Fragments.
Regards,
Vishu

1 reply

V
Adobe Employee
vish.dhaliwalAdobe EmployeeAccepted solution
Adobe Employee
March 9, 2020

Hello,

It is not possible to use the style system in the targeting mode. An alternate way to achieve that can be by creating the Experience Fragments [1] with different style options and then target using those Experience Fragments.
Regards,
Vishu
    N
    nadeensalvadorAuthor
    March 10, 2020

    Hi @vish.dhaliwal,

     

    Thanks! I tried this approach with the style system and got the selected styles to carry over to the other segments. Would this mean then, that for every segment, a separate experience fragment would have to be created, even if it is just a style difference?

     

    I also tried this approach to see if it solves the i18n issue wherein, when authoring for segments, the component seemingly disregards the current page language and keeps using the EN translations. Is this a limitation of the Personalization feature of AEM?  Is there a way to work around this? 

     

    Much thanks!

     

    Regards,

    Nadeen

    Terms & ConditionsAccessibility statement

    Loading footer...