Admin Site Using Translations When Shouldn't

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Author

Posts
June 1, 2017 at 12:23 am #381061

kairei
Expired Member

Post count: 78

I have a site with GD and WPML. I have my site language set to Japanese in WP and my default language set to Japanese in WPML. My personal profile language is set to English. This allows me to administer a Japanese site in English while letting end users see Japanese content on the front end. However, I just uploaded a new translation of the core GD plugin which includes admin site text strings. The GD strings show up in Japanese on the admin site even though my language is set to English. WP itself and every other plug-in I have installed are showing English in the admin site as per my language setting (and some of them do have Japanese translations). GD seems to ignore my language setting so I can’t use GD on the backend unless I go figure out which strings are admin strings and “untranslate” them. This seems like a bug but perhaps I’m missing something?

June 1, 2017 at 12:28 am #381063

kairei
Expired Member

Post count: 78

Note: the staging site used for my other post at https://wpgeodirectory.com/support/topic/translating-country-slug/page/2/ demonstrates the issue.

June 1, 2017 at 12:19 pm #381095

Kiran
Moderator

Post count: 7069

Hi kairei,

Can you explain steps how can i replicate it from my site? Did you checked for non GD plugin with same process?
GD have some custom fields translation which has texts saved for selected language, so may be it can be imported in different language.

Let us know.

Kiran

June 1, 2017 at 12:41 pm #381097

kairei
Expired Member

Post count: 78

Just go to the staging site referenced above and log into the admin site. You’ll see some of the GD stuff is in Japanese while no other plugin is. Notice that the logged in admin user’s language is set to English in their profile. GD is showing Japanese anyway. Change that user profile language to Japanese. Other plugins do change to Japanese. Change language back, other plugins switch back to English but GD continues to show Japanese. So, other plugins are working properly (i.e. by showing English when my language is set to English). Example, the “Insights” plugin.

June 7, 2017 at 10:58 am #382073

Kiran
Moderator

Post count: 7069

Hi There,

I have done same in my test site and i can’t replicate the problem there. I have used same settings with default language & admin language.

Can you provide me .po file which contains translated string in Japanese language? I have to check importing the file that you have imported.

Kiran

June 11, 2017 at 6:35 pm #382757

kairei
Expired Member

Post count: 78

This reply has been marked as private.

June 11, 2017 at 6:36 pm #382758

kairei
Expired Member

Post count: 78

This reply has been marked as private.

June 12, 2017 at 11:12 am #382803

Kiran
Moderator

Post count: 7069

Hi kairei,

I tries to import the .po file you attached in my test site and it worked fine without any problem.
Check screenshots attached
1) Admin > Edit My Profile > Language => EN > Save
2) Admin > Edit My Profile > Language => JA > Save

If you allow i want to try to import that file on your staging site.

Let me know.

Thanks,
Kiran

June 12, 2017 at 12:45 pm #382811

kairei
Expired Member

Post count: 78

Thanks. Sure, go ahead and import on staging.

June 12, 2017 at 2:08 pm #382848

Kiran
Moderator

Post count: 7069

Please check, seems it working fine now.

Kiran

June 12, 2017 at 9:49 pm #382922

kairei
Expired Member

Post count: 78

That’s weird. There must be something different between prod and staging. I just exported prod and re-imported it over staging so you can see the issue appearing on staging.

June 13, 2017 at 4:52 am #382942

Kiran
Moderator

Post count: 7069

It seems you have imported .po incorrectly. What steps you have followed to import .po file?

Steps that i followed:
1) Go WPML > String translation > Delete all the translations with domain “geodirectory”. To delete strings i ticked all the strings which have domain “geodirectory” & then clicked “Delete selected strings” button.
2) In Import / export .po section on same page upload file “geodirectory-ja.po” that you provided
3) Tick “Also create translations according to the .po file”
4) Select “geodirectory” from dropdown list “Select what the strings are for:” > click on “Submit”
5) On next page tick all the strings > click on “Add selected strings”

That’s it.

Please fix fuzzy translations in .po file you provided. To fix it i opened it with po editor selected all the strings and unmarked Fuzzy from top menu.

Kiran

June 13, 2017 at 5:59 pm #383058

kairei
Expired Member

Post count: 78

I followed your standard “translate core” instructions here:

https://wpgeodirectory.com/docs/translate-core/

I had no idea about this “importing” into WPML string translation thing. I saw no mention of WPML on that page… What is the difference in doing the “standard core” and what you describe above?

Also, what do the fuzzy ones have to do with this?

Thanks!

June 14, 2017 at 3:38 am #383105

Kiran
Moderator

Post count: 7069

Hi,

Instructions mentioned on page translate-core is uses WP standard translation method.
WPML(WordPress Multilingual Plugin) is a third party plugin that allowing your website to become multilingual. WPML has its own translation method like string translation.

Steps described in my last reply are for importing strings for WPML translation purpose when you have non EN has a default language.

> What do the fuzzy ones have to do with this?
< Follow this to know about fuzzy strings https://wpgeodirectory.com/support/topic/translation-16/page/2/#post-363540

Kiran

June 14, 2017 at 1:08 pm #383160

kairei
Expired Member

Post count: 78

So, do I not do the core translation steps at all and the Japanese core po/mo files are never uploaded?
Author

Posts