Plugin Author
Tim W
(@timwhitlock)
Loco Translate does not control what translations are presented to the user. It is a file editor.
You need to change your admin profile language setting, which is different from your site language setting. This is a feature of WordPress. If you have trouble with these settings please ask on a general WordPress forum.
Thread Starter
haytov
(@haytov)
I will explain
I already control the admin language and the site language.
BUT
when I translated a specific plugin, the backend was also translated.
it did translate only the frontend (as I wanted) until I changed the loco settings and saved the translation files to the SYSTEM (instead of AUTHOR which is the default)
Plugin Author
Tim W
(@timwhitlock)
when I translated a specific plugin, the backend was also translated.
My plugin doesn’t automatically translate anything. If you see translations that you didn’t enter then most likely WordPress has installed them.
I changed the loco settings and saved the translation files to the SYSTEM
Don’t save translations into this location. They may get overwritten. See FAQ https://localise.biz/wordpress/plugin/faqs/files-deleted
Thread Starter
haytov
(@haytov)
thank you.
about the location, I already read it, but I didn’t understand.
have to say I think your plugin is amazing, and this issue (the overwritten issue) is the only downside I find. I say it because I looked for a solution that I can understand, and I found a lot of people asking but with no good answer.
probably this explanation is aimed more at developers 🙁
Plugin Author
Tim W
(@timwhitlock)
The “good answer” is to place custom translations in Loco Translate’s safe folder, as documented. With your own files in place it shouldn’t matter what WordPress is doing with “installed” translations. If you want a particular string to stay in English (for whatever reason) you can simply save it in English and that will be used. Leaving it blank however is wrong. This will result in falling back to installed translations, which most of the time is the desired behaviour.
Forcing WordPress to NOT install translations at all is going to be technical because WordPress has no user-friendly option to prevent it from happening. Recently they made plugin updates optional, which IMO should prevent plugin translations from being updated too – but it doesn’t. Maybe they’ll fix that.
Thread Starter
haytov
(@haytov)
Thank you very much for your quick and helpful answer 🙂
