That being said, a lot of our customers have successfully been using our plugins with Polylang (which is also not supported officially at the moment).
I placed translation files in wp-content/languages/plugins/ but the bug is still there.
When translation file strings are not kicking in, it is usually caused by one of the following things:
Your translation files are not up to date
You are using some customized translation files that have been placed in the /wp-content/languages/ or /wp-content/languages/plugins/ folder. These might not be updated and will override any other file.
The strings are translated, but are considered “fuzzy”
In the first 2 cases, the solution is to update your translation files using the pot file. You can do this by using the Poedit software and heading to Catalog > Update from pot file.
In the last case, you will need to make them “unfuzzy” using Poedit.
In your specific case I am not sure exactly how QtranslateX handles priority. But I can tell you that the top priority normally goes to /wp-content/languages/plugins/
One quick test you could run would be to delete the top priority language files temporarily.
But you are probably better off trying to identify how QtranslateX sets priorities in my humble opinion.
Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.