Loco 2 issue with already translated strings
-
Hi,
I used your fantastic plugin several times and now I upgraded to v. 2, but I have a problem: when I modify an translation which I had previously created I don’t see the changes in the frontend.
I think there’s some confusion in the path to the translation files, or maybe Loco is not loading them and want to create new files.I see there’s a new safe location in Loco 2, is it better if I move the .po files there?
Loco says “This bundle’s configuration has been automatically detected, but isn’t fully complete. No translation template for the “discoverypro” text domain. One file can’t be matched to a known set of strings.”
I don’t think this is the problem, because it worked until now.Currently the languages files are in:
/wp-content/themes/discoverypro/languages/discoverypro.po (this is the original one)
/wp-content/languages/themes/discoverypro-it_IT.mo (my translation)
/wp-content/languages/themes/discoverypro-it_IT.po (my translation)The issue is if I open “discoverypro-it_IT.mo” with Loco and translate new strings or modify already translated ones, I don’t see them loaded when visiting the website!
- The topic ‘Loco 2 issue with already translated strings’ is closed to new replies.