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?
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.
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 to this feature-request
@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