This topic has 2 replies, 2 voices, and was last updated 1 years, 6 months ago ago by Rose Tyler
I have been using the Loco Translate plugin for Turkish translations on my WordPress site, which uses the Xstore theme. However, I’m having a recurring issue: each time I update Xstore theme or Xstore core, my translations revert back to English.
Every update requires me to translate the theme back to Turkish manually, which is a significant drain on time and resources. Ideally, I’d like to find a way to maintain my translations even after updating the theme.
I’m hopeful that there’s a way to keep these translated files intact so I don’t have to translate everything again after every update. I am looking for a detailed solution that I can implement to stop the translations from reverting to English.
I’d appreciate it if anyone with experience in this issue could provide some guidance.
Thank you in advance for your time and assistance.
Hello Admkts,
Thank you for contacting us and for using XStore.
Translation files of the theme should be placed in /wp-content/languages/themes/ folder,
plugins, like Core plugin, in /wp-content/languages/plugins folder,
with correct names, for example, for XStore theme: xstore-tr_TR.po, and xstore-core-tr_TR.po for XStore Core plugin, then you will not lose translation after the update – https://www.8theme.com/documentation/xstore/theme-translation/base-theme-translation/
We would recommend doing a backup of all the files before any update.
Also, after every update, you need to synchronize translation – https://www.8theme.com/documentation/xstore/theme-translation/translation-files-update/ Sometimes new strings are added, and only after synchronization, you’ll be able to translate new strings or strings that were changed. Not always, but some strings can be missing after the sync and you need to find and translate them one more time, this is independent of us and relates to WP functionality.
Kind Regards,
8theme team
Tagged: plugin, translate, woocommerce, wordpress, xstore
You must be logged in to reply to this topic.Log in/Sign up