Prevent Strapi AI Translations Overwrite Images and Dropdown Selections
K
Kate Lehkobyt
We’re using Strapi’s AI translation feature, which automatically triggers translations whenever we save changes to the English version.
Currently, this works well for text fields, but translated pages also contain images and dropdown selections (e.g. colors) that need to be added manually.
The issue is that every time we update and save the English version, the translation process overwrites the translated pages and removes the manually added images and color selections. This means we have to rebuild these elements on every translation update.
Could the translation logic be changed so that existing images and dropdown selections are preserved when translations are regenerated, while only the text fields are updated?
This would allow us to make regular content updates without losing manually configured localized content.
Alternatively, it would be ideal if the translation process could automatically copy the images and dropdown values from the English version to the translated pages. This would eliminate the manual work entirely, which is exactly why we’d like to make the AI-native Strapi functionality work seamlessly with our localization workflow.
林雄二朗
Since there are cases where you don't want to automatically translate text fields, I think it is preferable to be able to set fields that are not subject to translation.
For example, in cases where you want to set URLs for each language, there is a need to keep values for each language separately without applying automatic translation.
At the time of update, a specification that only updated fields are subject to translation may be fine.