Plugin Author
Tim W
(@timwhitlock)
If they really are stored under the global languages directory then plugin updates shouldn’t delete files. (I guess you know this)
Something else must be going on, but I don’t see how it could relate to this plugin because this plugin never deletes or moves files.
Hello, I really liked Your plugin, but I have the same problem. I can’t understand why after a while the translation comes back to the original. I tried to save in different ways, but the result is the same. The translation works, but after a day recovering. How the translation comes back? who does it?
Plugin Author
Tim W
(@timwhitlock)
I’d love to know too.
I don’t think you’ll find an answer on this forum as I’m generally the only person who responds to questions. As above I have no idea what process is to blame. It could be a caching issue, but whatever it is, I’m 99% sure it’s not related to my plugin.
Thanks for the quick reply. Most interesting is that this problem on several different sites. No-cache, no updates to any plugins. Only happens that the files returned are in their original condition. If I find a solution I will post it here. I was hoping someone had encountered this problem
Hello, I’m having the same issue in my site and, as Tim assures, not related to LoCo, I’ve tried changing translation files and uploading them with poEdit and the problem comes back …
Trying to get an answer from WooCommerce Authors.
Best Regards, and thank you so much for a plugin like LoCo Translate.
Raúl.
Hello,
I read this in woothemes :
Making your Localization upgrade safe :
If you keep your custom translations in woocommerce/i18n/languages (WooCommerce < 2.2+) they can be lost when upgrading. To make them upgrade safe, instead place them in wp-content/languages/woocommerce/. All translations will be automatically added to wp-content/languages/woocommerce/ with WooCommerce 2.2+.
https://docs.woothemes.com/document/woocommerce-localization/
LoCo uses the url wp-content/languages/plugins/ and woocommerce/i18n/languages but not wp-content/languages/woocommerce/. I think that’s issue 🙂
Hi,
thanks for the investigation..
I’ve given a try to create the woocommerce folder inside languages and have moved inside all .po .mo files related with woocommerce.
At least by the moment it works fine, will keep you informed…
Still no answer from woothemes staff.
Thanks again, I hope it’ll work ..
Regards,
Raúl.
Plugin Author
Tim W
(@timwhitlock)
Loco uses the url wp-content/languages/plugins/ and woocommerce/i18n/languages but not wp-content/languages/woocommerce/.
This statement is true, but files in wp-content/languages/plugins/ should still be safe from update processes.
Note that the path wp-content/languages/woocommerce is non-standard and Loco will not support this location in the 1.x branch of this plugin. (version 2 will)
The person who started this thread mentions specifically that they are using the “global path”. So do many other people reporting this same issue. For that reason, it seems this issue is not simply update processes overwriting files from the plugin folder. Anyone not using the global path can consider their issue solved.
For anyone else with files disappearing from safe locations, I am yet to find anything linking this issue to my plugin. Perhaps the original poster @soyrod could report back whether their issue has been resolved.
I am currently setting up a wordpress with WooCommerce. Whenever I modified translations in the file wp-content / languages / plugins /, wordpress was updating automatically translations and he overwriting my modifications. I resolved this issue with this solution and I had to leave Loco translate to poedit (it’s pity, because your pluging is very good). The files in folder wp-content / languages / plugins / should not change, but this does not seem to be the case for WooCommerce …
Plugin Author
Tim W
(@timwhitlock)
Thanks for the info. I guess WordPress must automatically pull official translations for this plugin then. That makes custom translations difficult without coding.
The files will change again using Loco or Poedit… it’s not a matter of LoCo.
They change even with loco uninstalled.
Plugin Author
Tim W
(@timwhitlock)
I think Rexchances’s point is that Loco can’t save files in the non-standard safe location, hence manual uploads into the safe folder are required. (manual uploads == POEdit)
Of course there’s no reason you can’t do your translations in Loco on a development server with auto-updates disabled – then simply deploy your MO files to a safe folder on your live sites.
Thank you Rexchances. I’ve placed the files in wp-content/languages/woocommerce/ and all but one site are functioning normally. One site translates back again, I think the case is in the theme of the site, in woocommerce files
Just a words to thank Rexchances his solution and say that, since I put my .mo . po files in the woocommerce folder, they have not been changed and everything is working smooth…
New .po and .mo files have been auto-created again at wp-content/languages/ folder, but the ones in use are those in Woocommerce folder, so will live with that. Only I’m sorry because this issue doesn’t let me use LoCo to make translations on the fly.
Tonight I’ve received WooThemes answer to my request:
“Can you tell me exactly what folder you are uploading your edited .po & .mo translation files to? Is it /wp-content/languages/woocommerce? If not, try uploading your .po & .mo files in that folder and let me know if the issue remains.
I hope that helps!”
So I think they don’t know what happens but point to your idea too…
Best regards and thank you all very much,
Raúl.
Plugin Author
Tim W
(@timwhitlock)
Thanks for the update Raúl.
I’ll point people to this thread when I get asked this question next time.
I’ll make sure version 2 of Loco Translate supports non-standard folder locations like this.
