Problem:
Mailchimp and other from plugins do use tooltips.
Solution:
Those strings are usually displayed in browser user language. So, there is actually no need to translate them. If you switch the browser language to German for example you should see how the content changes.
Actually each browser has it own way of displaying them, as thez are generated with JavaScript programatically.
Problem:
How to disable specific products for a specific language?
Solution:
The way to exclude products from specific languages is to simply not translate them.
Important is that you do not display the original content, as long a translation does not exist (fallback) which means you need to make sure to set WPML -> Settings -> Post Type Translation -> Products to "Translatable - only show translated items".
Another way, in case the products are already translated, would be to go to the products list and set those specific products as "Draft" or "Private", which will make them only visible to admin users.
Now you can find and translate the full code in WPML -> String Translation -> Under 'admin_texts_widget_custom_html' domain, especifically the '[widget_custom_html][10]content' name.
Problem:
I added all my pages to Translation Basket as per seen in tutorials. Since that happened I can't open Translation Basket
Solution:
If you do not have any translation in progress (beyond those that are stuck), you can reset it by following the steps below:
- Click on the WPML > Support > Troubleshooting
- Scroll down and look at the "Reset professional translation state"
- Select the "I am about to stop any ongoing work done."
- Click on the "Reset professional translation state"
Problem:
When I try to edit the page I'm getting redirected to this URL
"http://%26lang%3Den/"
Solution:
Edit the plugins-integration.php file found in the ../sitepress-multilingual-cms/inc/ folder and change the hook we use on line 113 to the following:
Problem:
Some taxonomies in your site are forced to be untranslatable. This is causing a problem when you're trying to run a multilingual WooCommerce site.
Solution:
1) Go to WPML > Settings > Taxonomy translation and make sure all the related product taxonomies are set to (click on the lock to unlock) 'Translatable - only show translated items' or 'Translatable - use translation if available if available or fallback to default language'. For example, product_cat (Product category) should be translatable.
2) Override any of theme XML rules for specific taxonomies by checking theme XML file in the theme root folder and change 0 to 1 (translatable).
or
Go to the WPML -> Settings page and click the Custom XML Configuration tab. Add the taxonomy rules as per our documentation.
Problem:
The original slug language is wrong. How do I change it?
Solution:
In order to change the language of slugs go to WPML> String translation and look for that slug. To change the language of specific strings, select them and click on the Change language button. Then, select a new language.
If you do not see some slug, add Translation in WooCommerce> Store URLs, and then it will appear in WPML > String Translation.
Problem:
Would you please help us in translating the interactive forms with Formidable PRO addon? We have tried already below solutions, none of them worked.
Solution:
It seems that the glue plugin between WPML and Formidable was not made to have the placeholder string available for translation.
Now, can you go to wp-content/plugins/formidable-wpml/controllers folder, edit the FrmWpmlAppController.php file, and make a change on line 606, please?
Basically, just change the code from this:
Problem: I need to show the same template in both languages, greek and english but only one works. The other shows the default layout of the theme.
Solution: There is a workaround for this issue provided by our specialists. Please follow these steps to apply the workaround:
- Create a full backup of the site.
- Modify elementor-pro/modules/theme-builder/classes/conditions-cache.php Lines 96 - 101:
- Re-save the Display Conditions for each template.
Could you tell me if the workaround solves the issue?
Important note - This workaround has two effects:
1.- The conditions start working for all languages
2.- When you search for posts or pages etc in the Display Conditions dialog, ALL language posts are returned. This is more of a cosmetic issue but just so you know.
Problem:
WordPress found a fatal database error on the Website that looks this way:
COLLATION ‘utf8_general_ci’ is not valid for CHARACTER SET ‘utf8mb4’
Solution:
The reason for this issue is that various database tables use a different collations.
To solve the issue a matching and similar collation for all DB tables.
You can run the following MySQL query to solve such an issue, but it will need to be adjusted with the matching table prefix and also in case a different collation is used than mentioned inside the query:
ALTER TABLE wp_posts CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
Problem:
On the translated pages in English, the links are pointing to the original Dutch pages instead of the translated English pages.
Solution:
You need to translate the page and finish the translation job.
- Go to WPML->Translation Management-> Send the page for translation and then take the translation job.
- Translate 100% and save.
Problem:
My problem now is that I want to add en-GB as a language. When I try to add English with a code of 'uk' I get an error that 'The Language code already exists.'. I assume this is because the database is pre-populated with Ukraine as a language. This is not unreasonable, but people in the UK often refer to the country as UK not GB, and even if I could change my folder for UK English to be GB it is pre-existing as UK, so this would cost me in SEO which I cannot accept.
Solution:
Deleting a language from WPML is not a good idea.
Instead, you can go to WPML → Languages → Site Languages, press the Add / Remove languages, add the Ukraininan language, then press the Edit Languages link. This way you'll be able to "transform" Ukrainian into UK English.
Problem: We are using the Salient Theme and our problem is that the link of the button module of the vpbakery implementation is not pointing to a translated site but to the original
Solution: I added the following code in WPML -> Settings -> Custom XML Configuration tab:
I would like to ask you to follow these steps:
- Go to WPML -> Settings -> Activate Classic Translation Editor
- Edit the test page in German -> Make a small change in the content -> Save the changes -> Update the translation.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive