Is it possible to set the same focus-point for all languages?

šŸ†˜ Support
1

One of our content-editors noticed that the focus-point of images has to be set individually for every language. This can become quite cumbersome for a setup with several languagesā€¦ we also donā€™t see the benefit of having an individual focus-point for every language.
Is this something that could be toggled? Eg. make the focal-point translatable or opt-out of translation?

Any advice is highly welcome

2

Hello @tools1

The best way to do so would be to make the Asset field that the image is in not localised, that way it will maintain the focal points across all locales.

1 Like
3

Hi @m.finamor
I have to come back to this problem, since itā€™s only partially solved.

For ā€œModelsā€ itā€™s easy to disable localisation on individual image-fields. However, we have Blocks that contain images, as well as text-content (which should be translatable).

When we add a ā€œModular Contentā€ field on one of our models (with enabled localisation for the modular content), then the images will also become translatable, resulting in the problem with the ā€œtranslatedā€ focal-point.

As a lot of our ā€œpage-contentā€ is based on modular blocks, the problem shows up quite often.

4

Hello once again @tools1

I see, however there are only a couple solutions i see for your use case:

  • Splitting the image and the localized text fields into two blocks, and localizing only the text one
  • Adding on our end a way to localize image fields but mantain focous points across locales (which seems very counter intuitive for the majority of other use-cases)
  • Adding on our end a way to localize fields within blocks, which is requested in this feature request right here: Allow localised fields within blocks

For now the immediate option seems to be only the first one, or to set the focal point on all locales manually unfortunately

5

Hi @m.finamor
Thanks for your swift reply.
We have content-blocks that need to have image and text fields in the same block, so separating them wonā€™t work. But since the ā€œlocaliseā€ Option is on the ā€œModular Contentā€ field, this solution wonā€™t work anyway, right? Since localising a Modular-Content field results in all allowed blocks to be localised.
We just use a single Modular-Content field and the editors can then create the different content-blocks there.

Having localisation on the block-level would be better in this case. So Iā€™m also giving a :+1: to this feature-request :smile:

6

@tools1 , yes, sorry, i meant splitting them in two different blocks, and then splitting those blocks usage in two different modular content fields, e.g: one non localized modular content field called ā€œImagesā€ for non localized content assets, and one localized modular content field called ā€œTextsā€ with the text fields