{"section":"known-issues","requestedLocale":"en","requestedSlug":"saving-cms-content-in-a-nondefault-binding-locale-can-silently-overwrite-the-defaultlocale-content-and-hide-the-correct-translation","locale":"en","slug":"saving-cms-content-in-a-nondefault-binding-locale-can-silently-overwrite-the-defaultlocale-content-and-hide-the-correct-translation","path":"docs/en/known-issues/CMS/saving-cms-content-in-a-nondefault-binding-locale-can-silently-overwrite-the-defaultlocale-content-and-hide-the-correct-translation.md","branch":"main","content":"## Summary\n\nWhen editing page/block content in Site Editor on a store with multiple supported locales, saving a translation for a locale other than the store's default can, in some cases, overwrite the original default-locale content rather than create a separate translation. This corruption is usually not visible on its own, but if the affected text also has an extra space at the start or end, the storefront may display the wrong-language text for that content, even though the correct translation exists.\n\n## Simulation\n\n1. On a store with 2+ supported locales, save a text block in Site Editor while the language selector is on the store's **default** locale.\n2. Reload the page, then edit and save the **same** block again with the language selector on a **different** (non-default) locale.\n3. If the affected text has a leading or trailing space, viewing the page in the locale that should show the original content may instead display the text saved in the other locale — even though the correct translation still exists.\n\n## Workaround\n\nManually trim leading/trailing spaces from the text before saving in Site Editor."}