Problem: The client is experiencing an issue where the Elementor interface is translated into the language of the site they are editing, and they want to keep the Elementor editor in English regardless of the site's language.
However, we also offer a workaround: 1) Perform a full site backup (this is mandatory). 2) Navigate to the
wp-content/languages/plugins
folder. 3) Locate the Elementor MO & PO files (e.g., elementor-sv_SE.mo, elementor-sv_SE.po). 4) Delete or move these files from the directory. 5) Clear all types of caches.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket: Contact WPML Support.
Problem: The client needed to hide membership options on their website when the current language is set to Chinese, as the 'alipay' payment method does not support 'Membership' features for Chinese customers. Solution: We recommended using CSS to hide specific elements based on the language. The correct CSS code to add under Appearances > Customizer > Custom CSS in WordPress is:
This code targets the HTML language attribute for Chinese ('zh-hans') and applies a style to hide the membership elements. Additionally, for translating menus and content, we suggested using the manual translation options provided by WPML. You can find more details on translating menus manually at Translating Menus Manually and using different translation editors at Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues with links not being translated correctly, resulting in 404 errors or linking to the wrong language version of the page.
Solution: We recommend two approaches to resolve this issue: 1. As a long-term solution, add
<type="link">
to your existing XML configuration. This will ensure that links are correctly translated. 2. As a short-term solution, use machine translation for the URLs and manually edit the translations if they are incorrect.
We advise the client to implement the first solution for a permanent fix. However, it is important to note that updating existing pages that use shortcodes from the previous XML configuration will be necessary to make the changes effective.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem:
I have an automatic translation of some posts and the portfolio, but the images are not showing. The theme I am using is called Kallyas.
Solution:
This is an option from the Kallyas theme and the images are saved in a custom field. All you have to do is to go to WPML → Settings → Custom Fields Translation and set the zn_port_media custom field to copy.
Once I go back to the original portfolio item and simply hit the Update button, the images appeared on the translation too.
Problem:
The translation I need is for a javascript popup window which I think is generated by browser or something else. The popup window has two buttons Close and Cancel. As you will see from the code above, the text of those buttons is not defined in the script and rather the script just calls a function to show the popup.
So I need to translate the words Close and Cancel. Solution:
Unfortunately, it is not possible to translate these strings into JavaScript. To do this, you must use custom code. You can localize these strings by using the "wp_localize_script" function: https://developer.wordpress.org/reference/functions/wp_localize_script/
This is necessary because WordPress currently only offers a localization API in PHP, not directly in JavaScript.
In the 'Example' section of the link above, you can check that it'll create a JavaScript code having an object "object_name" with some values, among these values the "some_string".
This code must be within PHP (usually, the recommended file is the functions.php of your theme). To access the JavaScript object, you will only use values that have already been defined within your PHP file.
That is, they are two pieces of code that are going to be defined in two different places. One is PHP (functions.php of your theme), so you can define the translatable string. The second part will be the JavaScript object inside the JavaScript file that you want to use it.
Problem:
We are using Smart Slider and Elementor on our website but we can't translate the slider.
Solution:
You can translate the smart slider with the following steps:
1- In your admin dashboard go to Smart Slider > Dashboard
2- Switch the admin language to the second language from the top admin bar
3- Duplicate the English(the default language) slider
4- Edit the duplicated copy and translate the texts
5- Save the changes
6- Go to Pages >All pages > Switch the admin language to the second language
7- Edit the translated page with Elementor and use the new slider you just created
Problem: If you're using WPML with Bold Builder and encountering issues where custom element translations made directly on Pages are erased when using the WPML translation editor, this might be due to the elements not being registered as translatable. Solution: First, ensure that the custom elements are registered in WPML to be translatable. You can do this by adding the necessary XML configuration in WPML-> Settings-> XML Configuration. Here is an example of how to register a custom element:
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with WPML updates failing due to the hosting server's inability to whitelist certain domains necessary for the updates. Solution: We recommended that the client ask their hosting provider to whitelist the domains: wpml.org, cdn.wpml.org, and api.wpml.org. Additionally, updating OpenSSL on the server might resolve the issue. If the hosting provider is unable to whitelist these domains, we suggested manually updating WPML by downloading the latest versions from https://wpml.org/account/downloads/ after creating a full website backup and removing the existing WPML plugins. Alternatively, changing the hosting provider could be considered.
If this solution does not apply to your situation, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with currency shifting and stock updates on their WooCommerce site when NitroPack caching is enabled. The currency selection is supposed to be based on the client's country, but it sometimes fails to change correctly. Additionally, product stock levels are not updating as expected. NitroPack support inquired about the use of variation cookies related to the WooCommerce Multilingual plugin, which the client could not find in the session.
Solution:
1) We confirmed that the necessary cookies for handling languages and currencies already exist, and one of them is a NitroPack cookie.
2) We invited NitroPack to collaborate with us through the Go Global Program to ensure compatibility between our plugins.
3) We provided a code snippet to create a custom cookie for currency:
4) We advised the client to add this code to their functions.php file and to ask NitroPack how to exclude the 'wcml_custom_currency_cookie' from caching.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is trying to register WPML on their WordPress site and has followed the step-by-step instructions but is experiencing issues.
Solution: If you're experiencing issues with registering WPML on your site, we recommend you try the following steps: 1. Log in to your WPML account and go to the Sites page. 2. Delete the existing site key. 3. Create a new subscription key for your site. 4. Visit your Site Dashboard and navigate to Plugins >> Add New >> Commercial tab. 5. Click on the “Unregister WPML from this site” or “Register” button. 6. Register with the new site key and refresh the page.
For more detailed instructions, please refer to our documentation:
Problem:
I read quite some threads about this topics already, but I am still not sure what is the best option to use in my situation, could you help me?
Some basics:
- We have an English website with a lot of content.
- We want to translate only a part of it (e.g 30% of the pages) into Spanish
- We want to use Advanced Translation Editor
- We use Elementor page builder
So we should be able to:
1. Translate full pages from English into Spanish with the Advanced translator Editor
2. Once a page is translated, go to the Spanish page in Elementor page builder and make some modifications (e.g remove a section or links to pages that don't exist in Spanish. Since only a part of the Website is translated, some sections are linking to non existing content in Spanish and we should remove them.)
3. In the future, when the original English page is updated, we should be able to translate these modifications via the Advanced translator Editor into Spanish.
Solution:
In this case, the best alternative is to translate the content manually. Therefore, it would be Option 3: Duplicate and "Translate independently".
If you use the Translation Editor to translate the content, edit the Spanish version with Elementor to have a different design, it'll be overwritten when you make a modification in the original page, and update the translation. You can check by yourself this behavior:
- Translate a page with Advanced Translation Editor or Classic Editor
- Edit manually the translated page with Elementor
- Make a small change to the default page
- Update the translation and check that the edition you made will be overwritten with the original page layout
So, in order to avoid this and use manual translation, please follow these steps:
- Open the page/post you want to translate manually
- In the Language box, turn off WPML’s Translation Editor switch found in the ‘Translate this Document’ section
- In the 'Use the WordPress Editor to translate' pop-up dialog that appears, select 'This page' option
- In the Language box, select the Duplicate checkbox, and then click Duplicate. This will duplicate the page in the selected secondary language
- Click on the pencil icon to edit the page in the other language
- On the editing page of the duplicated page, click 'Translate independently' in the Language box
Some themes, like The7 theme, allow you to set logos via theme options.
If you want to use a different logo per language, you need to translate the logo ID in String Translation. This tells WPML which logo to display in each language.
If you cannot find the default language logo ID on the String Translation page, you can click the Translate texts in admin screens link to add it to the String Translation table.
Problem:
Learndash courses disappeared from the frontend after updating to WordPress 5.8
Solution:
The debug log file showed the following error:
PHP Fatal error: Uncaught InvalidArgumentException: element_id and type do not match for element_id:42 the database contains post_attachment while this function was called with post_post in xxxx/wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-set-language.php:34
And it was fixed with the following steps:
Go to WPML > Support > Troubleshooting page, then click these options:
- Clear the Cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Fix WPML table collation
- Set language information
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
