Problem:
i am using multisite concept , then why i need to register again and again to each website with wpml
Solution:
You only need to use one site key for all your multisite installations. Add the OTGS Installer plugin to your network and register it. When you activate the WPML plugin on your subsites, it will already be registered.
Problem:
Translated versions of pages were redirecting to the default language for all the pages and posts.
Solution:
After detailed investigation, I found that "SEOPress Pro" plugin was creating this issue. Deactivating the plugin resolved the issue and everything went back to normal.
Note that "SEOPress" plugin is compatible with WPML, which was also active in the site, but the Pro version wasn't. So asked the client to contact plugin author since their base version is already working.
Problem:
When I select all strings for context toolset-forms-32761, and click the button "Delete selected strings" I expect all those strings to be deleted.
Instead, I got:
Clicking the button "Delete selected strings" has no effect. Solution:
Updating the plugins solved the problem. It's a bit weird, since I have deleted many strings in the past. But as long as it's working, I'm fine with that!
WooCommerce Germanized email content not correctly translated.
Solution:
The issue was due to the language settings of the user who is placing the order and the admin who is viewing or triggering the order email from the WordPress dashboard.
In the front end:
- If the order is submitted in English, the order email will be in English.
- If the order is submitted in German, the order email will be in German.
In the WordPress Dashboard > WooCommerce > Orders:
- If you change or trigger the email sent from the WordPress dashboard, the language of the Admin user will be considered.
- If you want to send from the dashboard in English, go to WordPress Dashboard > Users > Profile and change the Admin language to English.
Make sure you have translated both instances of the text in the WPML String Translation.
Sometimes, you may not be able to find the strings you're looking for in the String Translation table. How you translate them depends on the theme or plugin they're coming from, and how they were implemented in the theme or plugin.
Problem:
The client wants to dequeue WPML stylesheets from the code for optimization purposes.
Solution:
To disable the “wpml-legacy-horizontal-list-0-css” and “wpml-menu-item-0-css” files, please add the below code in your theme functions.php file:
Problem:
The client wants to add a translation inside a variable
Solution:
- First wrap the string in the gettext function like this: https://wpml.org/forums/topic/adding-wpml-translation-inside-a-variable/#post-13172685
- After that, please scan the theme in which you update the code from WPML >> Theme and plugins localization page.
- Go to WPML >> String Translation page and search for that string and add the translation.
Problem:
I can't make the Philipines (Tagalog) language automatically translated because the mapping language doesn't exist for this language.
Solution:
The Philipines (Tagalog) language is not supported by any of the translation engines used by WPML as you can see here https://ate.wpml.org/mt_langs
Since it's not supported, you won't be able to use the automatic translation for this language.
Problem:
Automatic translate does not translate existing content on the site automatically. Solution:
Go to WPML > Settings > Translation Mode > Switch to Translate Some and back to Translate Everything > Select the option to translate existing content. https://monosnap.com/file/VLaUIjJ0qZrAsD3Tk5RvSFgXhBwMQE
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
