Embed components localization

Support
1

Hi,

We’ve come to the need of having more complex structure with localization requirements and we intended to Embed Components to achieve this, here’s a simplified structure of what we want:

Schema

  • Field A (string)
  • Field B (string)
  • Field C (embedd component)
    • Field AA (string) - Localizable
    • Field BB (array)
      • Field AAA (string) - Localizable
      • Field BBB (string)
  • …

But going this way will not activate localization on nested components.

As far as I can see this topic was already discussed here so no we are left with these solutions:

  • We make the whole reference component localizable (Field C is example structure) and it’s up to the content creator to ensure that the structure is equivalent across all languages (they did not miss a line in the Field BB for example)
  • We use References but this does not make sense for us as nothing will be shared between contents, so we will end up with a lot of content that are “referenced” yet used only once.

Are we understanding those limitations correctly ? what would be our best apporach for handling our need ?

Thanks.

1 Like
2

This is the actual feature request: Localizable components - #6 by Sebastian

Just vote for it or comment. The solution would be references at the moment.

3

Hi,

Thanks for the clarification, I indeed voted for this feature that could come in handy for us.

Thank you.