Problem:
Message :
There is a problem with the String Translation table in your site. This problem is not causing a problem running the site right now, but can become a critical issue in the future. WPML support team knows how to fix it. Please add a message in the relevant support thread and we'll fix it for you.
Solution:
We've found some edge cases where this error is fixed following these instructions to recreate icl_tables:
- Make a full backup of your site (files and database)
- Please add this code to the bottom of the functions.php file in your theme's root folder
- Visit your site's homepage at least one time
- Remove the code
Once you complete these steps, then you have to remove the keys "wpml_string_table_ok_for_mo_import" and "wpml_notices" from the options table (by default wp_options, where "wp_" is your database prefix), and all errors should be gone.
Problem: The client is trying to calculate the cost in credits to translate their entire site. Solution: We recommend getting the word count of the website by following the steps in our documentation on Getting Your Website's Word Count. Once you have the word count, multiply it by the number of credits per word, which can be found on our Automatic Translation Pricing page. Then, refer to the pricing table to estimate the total cost.
Problem: You are trying to translate links from buttons created with Flatsome's UX Builder. While you can translate the text through String Translation, you are unable to translate the URL behind these buttons. Solution: We recommend following the tutorial for translating pages/posts created using UX Builder, which can be found here: https://wpml.org/documentation/theme-compatibility/create-multilingual-websites-using-flatsome-and-wpml/ Additionally, please update your language configuration code as follows:
After updating the code, please update the original language page and then its translation to see if there is any difference in the results.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 needed, please open a new support ticket for further assistance at https://wpml.org/forums/forum/english-support/.
Problem: The client is receiving error messages from SEMrush for six sites indicating that there is "No self-referencing hreflang" for pages such as https://www.nimbo.net/bewertungsmethoden/. Solution: We have reviewed the URLs provided and found that they do include self-referencing hreflang tags. For instance:
If you're experiencing this issue, we recommend checking the source code of the page that is reportedly missing the self-referencing hreflang tag. If it is indeed missing, please update the source code accordingly. If you find that the self-referencing hreflang is present, the error may be a false positive from SEMrush.
If this solution doesn't look relevant or if you need further assistance, please open a new support ticket with us.
Problem: If you're experiencing an issue where Arabic text, such as the title of content, is displaying with broken letters and gaps between them, Solution: 1) The problem is likely due to the CSS attribute
Letter-Spacing
. You can either disable this attribute or reduce its value to resolve it. This can be done by writing separate CSS for the Arabic headings or by editing the translated pages using Elementor and modifying the heading element. Here is a helpful video: https://files.fm/f/q6vznmwnz
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
