Expand my Community achievements bar.

Customization to support Non-Translatable Content Updates on Multiple Language/Locale sites?

Avatar

Level 2

The issue we are facing is when we update non-translatable content within a blueprint component (image or URL update for example), and we don't necessarily want to overwrite our live copy page which has already been translated to French. For example, the home page on our en_ca site. Let's say it is copied down to fr_ca (French Canada). Let's say I want to update the hero component image only on en_ca and want that change to take effect on fr_ca. Our rollouts are set up and the image change happens correctly but the problem is that when we activate this page with the change, the entire English page overwrites on the fr_ca home page so it's now back to English (because the blueprint page is in English) when all we wanted to do was update the image. How do we prevent this from happening? It's not feasible to send the page through translations again when all we did was make an image update. This would apply to URLs as well. We need to be able to make non-translatable content updates and not overwrite our translated pages. Are we missing something in the set-up or in configs? Or is this custom development? Please help!

1 Reply

Avatar

Level 10

Hi,

Are you using any OOB rollout configurations or the custom rollout configuration ??

If you use 'Standard Rollout' configuaration which is OOB, you should see only the updated changes in the live copy as it uses 'contentUpdate' action. You can refer [1] to get more details

[1] contentUpdate