Additional strings

Loco Translate will only read the MO file if there is no corresponding PO file.

Did you also upload your modified PO file?

Yes, I did.

Hm, strange. I just did it again. Uploading po and mo file and now the string is available. Strange thing. Thanks a lot.

But, now the string is not translated on the frontend. I am testing with leave a reply only to find out the right approach.

Maybe it is related to the same issue that I have with translation of woocomerce related products title. I am changing the translation string and it is ok on the frontend and after a while it’s revert to previous translated string?!

• This reply was modified 8 years ago by Asclepius.
• This reply was modified 8 years ago by Asclepius.

after a while it’s revert to previous translated string?!

Perhaps an external process is overwriting your files. See https://localise.biz/wordpress/plugin/faqs/files-deleted

Verify whether the actual files are being replaced.

I read that already. What do you suggest to make a wp-content/languages/loco directory manually and to move files there? Because there is already a wp-content/languages/plugins directory?!

I am a little confused.

• This reply was modified 8 years ago by Asclepius.

wp-include has nothing to do with translations. I don’t follow your question.

Did you verify whether your files are being overwritten?

I ment wp-content/languages/loco, my mistake

I change the translation for example on related product locally by Po Edit and upload and overwrite and so far the translation change remains.

But the comment form strings are not changed. ?? Even if I did the above operation for them too. Still in english.

• This reply was modified 8 years ago by Asclepius.

Your comments are confusing. You said “it is ok on the frontend and after a while it’s revert to previous translated string”. Now you say “so far the translation change remains” but also “the comment form strings are not changed”

Please be clearer. Are your changes reverting or were they never working in the first place?

Also, can you confirm whether you have the same problem using POEdit that you do using Loco Translate?

1. First issue

Related products translation is changed via loco. And then after a while the translation is back to first one prior the change.

And then I changed the translation locally via the Po Edit and then upload via ftp. So far the change remains.

The loco plugin does something, when is not used it’s okay.

2. Second issue

I am adding new strings into the po file locally and then I am uploading them via ftp and nothing changed on the frontend, i.e. strings are not translated on the website.

This unstable behavior cost me more than 6 hours today :).

Anyway, so 1st issue now is stable (I hope). 2nd issue remains. How to force to work the translation?

You suggested safe locations.

Do I have to move the theme po and mo files to wp-content/languages/loco (I have to create loco dir manually) or to move to wp-content/languages/plugins/loco?

The 2nd issue is the same for wp site map page plugin.

Please, advise.

• This reply was modified 8 years ago by Asclepius.

The loco plugin does something, when is not used it’s okay.

My guess is that your FTP uploads have different file permissions from files saved by Loco Translate. This would confirm what I’ve already said, that WordPress will overwrite your files if you don’t protect them.

If uploading files from POEdit via FTP works for you then I suggest you keep doing what works.

I am adding new strings into the po file locally and then I am uploading them via ftp and nothing changed on the frontend, i.e. strings are not translated on the website.

Ok, so you have the same problem using POEdit that you do with Loco Translate. This suggests the problem is not with the editor, but with something else you’re doing.

What about the code that displays these translations. Did you add that to the theme yourself? Can you show it to me?

You suggested safe locations. Do I have to move the theme po and mo files?

I suggested this to solve your first problem. Not your second. You said your first problem is under control.

In answer to your question though – the safe location for theme files is wp-content/languages/loco/themes/<textdomain>-<lang>.mo. You should always use this location if your theme allows you to, but it will not force your missing translations to show up. This is a separate issue.

• This reply was modified 8 years ago by Tim W.

The code in the theme is added by the theme developer when it’s bought. No changes on that. The text domain is all the same for the theme on these strings.

I am surprised how some strings applied and when a new added they are not applied. Same text domain in the same po/mo file.

How do we proceed?

• This reply was modified 8 years ago by Asclepius.

I don’t have any information to proceed with, and you’ve already said you have the same problem if you upload from POEdit. Is that correct?

If you’ve uploaded a valid file to a valid location and the theme code is valid, then I’m out of suggestions.

Yeaaah, everything is valid :). Maybe will put the translation hard coded. ??
Thank you so much.