June 17, 2015 at 5:05 am #38469
Trying to setup the basic Posts Locator Using on a bilingual setup (French / English). What’s Pretty weird — and I can’t find a solution — is: that even if I browse my site in English, all information shown by Geo MyWP is in French.
I deleted the plugin;
Still the same 🙁
Everything will only show in French.
I’m really puzzled.
Any help will be greatly appreciated.
YvesJune 17, 2015 at 5:33 pm #38525
How exactly do you set it to be bilingual?June 17, 2015 at 6:38 pm #38535
Hey! Thanks Eyal for Checking in 😉
I am setup like this:
qTranslate (Manage Languages)
Loco Translate (Manage Translations)
This setup works with 99% of the plugins I use.
But for some reason… that I just can’t pinpoint…?
Is there something I just can’t see? 😉
YvesJune 18, 2015 at 3:53 am #38579
I made some progress.
There seems to be a problem with the French Files :
When I remove these, then I can get the English version to work fine.
Let’s see if I can pinpoint something in there…
YvesJune 18, 2015 at 7:00 am #38587
For me there was a problem with the French translations files:
I completely deleted these two files;
Refreshed the Frontend;
All is behaving as supposed for English.
With Loco Translate, I started on my own translating to French (fr_FR) only the Frontend strings I need.
So far, all behaves OK. 🙂
YvesJune 18, 2015 at 8:19 am #38590
No. I was wrong.
I am encountering again the same issue.
It is something else. ????
Puzzled …June 18, 2015 at 8:32 am #38591
Procedure to recreate:
01. delete all language files from geo-my-wp/languages;
02. Browsing the site in English, all geo-my-wp data is presented with English:
Address: The address here
So far so good for my English Website version
03. Move in geo-my-wp/languages my previously created localization:
Result: Browsing the site again in English, all geo-my-wp data is presented with French:
Adresse: The address here
Site Web: testdomain.com
Puzzled ???June 19, 2015 at 5:14 am #38652
I am not sure at the moment but maybe for some reason GEO my WP is not compatible with qTranslate plugin.
Once I am done with the version of GEO my WP that I am currently working on I will test the qTranslate plugin.
Meanwhile I advice you to contact the developer of qTranslate plugin and describe him the issue. He might be able to give an advice or he might know what causes the conflict.June 19, 2015 at 11:06 am #38684
I’ll see what I can find on qTranslate side.
Will let you know when I find something…
Take care 😉
YvesJuly 6, 2015 at 2:59 pm #39723This reply has been marked as private.July 8, 2015 at 6:31 am #39891
Hi Eyal 🙂 !!!
I applied this fix that John Clause (qTranslate Team) kindly suggested and it works 🙂
change the line at the end like this:
The initialization of the strings in trouble must happen after the language is detected and set. Action ‘plugins_loaded’ is the one where WP recommends to call load_plugin_textdomain. In theory…
I can confirm, It works !!!
YvesJuly 8, 2015 at 10:53 am #39896
Please thank John Clause for me for providing you with a fix :).
I apologize I am not very responsive at the moment but I am out of the country with limited internet access.
I am glad the fix is workgin for you at the moment. I will provide an official fix in the next release of the plugin.
You must be logged in to reply to this topic.