Problem: The client was experiencing an issue where a page, despite being fully translated, still appeared as 'Needs translation' in the WPML translation queue. Additionally, attempting to translate the page resulted in an error message indicating that WPML had failed to translate the page three times.
Solution: We recommended the following steps to resolve the issue: 1. Create a full site backup. 2. Navigate to the Translation Dashboard, locate the translation job for the affected content, and cancel it if possible. 3. Edit the content in the original language, make a minor change, and save. 4. Reassign the content for translation to yourself via the Translation Dashboard. 5. Update the translated version of the content through WPML -> Translations. 6. Check if the issue has been resolved.
DELETE FROM `wp_postmeta` WHERE `meta_key` = '_icl_lang_duplicate_of';<br />DELETE FROM `wp_icl_translations` WHERE `language_code` = '';
If the problem persists or the solution seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues (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 at WPML support forum for further assistance.
Problem: You are encountering an issue where the table 'u688877668_AZCbX.wp_icl_strings' does not exist in your database, which is causing problems with the WPML plugin. Solution: 1. We recommend creating a full site backup before proceeding with any changes to ensure your data is safe. 2. After backing up, you can attempt to resolve the missing table issue by following the workaround provided in this documentation. 3. Additionally, it's important to ensure that your WordPress memory limit meets the minimum requirements for running WPML effectively. You can increase the memory limit by adding the following code to your wp-config.php file:
Make sure to place this code above the line /* That's all, stop editing! Happy blogging. */. 4. You can verify the current memory limit in the WPML -> Support section of your WordPress dashboard.
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 further assistance is needed, please open a new support ticket.
Problem: The client reported that a coupon was functioning correctly in the primary language (English) but not in the secondary language (German). This issue was due to the add-to-cart URLs not being translated to match the product variations in the secondary language. The Elementor Price Table widget used did not automatically present URLs for translation, which is necessary for proper functionality in a multilingual setup.
Solution: We recommended ensuring that the 'Make themes work multilingual' and 'Language filtering for AJAX operations' options were enabled under WPML >> Languages. The client was advised to manually translate the add-to-cart URLs to correspond with the translated product variations. This involved editing the page in the original language, switching to the secondary language, and setting the correct URLs for the buttons. Additionally, the client needed to register the Elementor Price Table element using a custom XML configuration to make the URLs translatable by WPML. Detailed steps for registering custom Elementor widgets for translation can be found here: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 problems persist, please open a new support ticket at our support forum.
Problem: You are working on a site under development and want to have uppercased translations of custom post type slugs using WPML. However, when you enter an uppercased slug, it saves all as lowercase. Solution: Unfortunately, it is not possible to save uppercase slugs due to a restriction from the WordPress core. WordPress only allows lowercase letters in slugs. You can read more about this restriction on this link.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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.
Problem: You are trying to translate your site using WPML and WPBakery but encountered a PHP Fatal error: Uncaught TypeError related to the
substr()
function in the WPML plugin. Solution: We recommend updating your WPBakery Page Builder plugin to version 8.6.1. You can find the release notes and update instructions here: https://kb.wpbakery.com/docs/preface/release-notes/ If updating does not resolve the issue, try temporarily disabling all plugins except WPML and WPBakery Page Builder to isolate the problem. Ensure you take a full backup of your site before making any changes.
If these steps do not resolve your issue, or if the solution provided here becomes 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client is experiencing a 'Download failed. (Forbidden)' error when attempting to update or download WPML plugins, even after deregistering and registering the sitekey. Solution: 1. Revalidate your domain with your sitekey by navigating to https://wpml.org/account/sites/ and copying the sitekey created for your domain. Then, go to WP > Plugins > Add new > Commercial Tab > Deregister and register the sitekey again. 2. If the issue persists, manually install the plugin. Download WPML manually by visiting https://wpml.org/account/downloads/, scroll down, and click on 'Download WPML manually'. Then, in your WP dashboard, navigate to WP > Plugins > Add new and upload the downloaded zip file directly.
If these steps do not resolve your issue, or if the solution becomes outdated, we 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 encounter problems, please open a new support ticket at WPML support forum.
Problem: The client enabled Pay-As-You-Go for their website, but the site won't automatically translate until all translations are complete. The site appears stuck and won't automatically translate because the client has reached the credit limit. Solution: We advised the client to either pay for the used credits or assign more credits from their WPML.org account to continue translating. This can be done through the WPML account management area. Additionally, for changing the WordPress backend interface language to Chinese, we recommended going to Users → Profile page on their WordPress site. For further guidance, we suggested checking the documentation on setting the WordPress administration language, which can be found here: https://wpml.org/documentation/getting-started-guide/language-setup/setting-the-wordpress-administration-language/.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where the product category page displays a sidebar in the translated language, but not in the main language. Solution: 1. Verify if the product categories are using a template and ensure this template is translated via WPML. Follow the guide on creating multilingual websites using the Woodmart theme and WPML: https://wpml.org/documentation/theme-compatibility/create-multilingual-websites-using-woodmart-theme-and-wpml/ 2. Increase the WordPress memory limit to at least 128MB. You can add the following code to your wp-config.php file:
Add it above the line /* That's all, stop editing! Happy blogging. */ You can check the current WordPress memory limit in WPML -> Support.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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.
Problem: The client is experiencing an issue where special characters like the en dash (–) are being replaced by a regular hyphen (-) in translations using WPML. This alteration occurs regardless of the translation method used, affecting the intended formatting of product titles and descriptions.
Solution: We conducted detailed tests using both automatic and manual translations across different language pairs and translation services. Here are the findings: 1. When using PTC for translations, the issue does not occur. The en dash remains unchanged in both the Advanced Translation Editor (ATE) and on the frontend. 2. When using DeepL, the en dash is replaced by a regular hyphen in the ATE, but it displays correctly as an en dash on the frontend. This inconsistency is due to DeepL's internal grammar rules, which we cannot alter.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, visit our support forum.
Problem: The client is unable to see product variations on their website, only seeing an 'add to cart' button instead of options to choose variations. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Ensure you have a backup of your site for safety reasons. 2. Navigate to WPML >> Taxonomy Translation. 3. Select the Product Size attribute. 4. Click the
Synchronize attributes and update product variations
button if it's enabled. 5. Clear all site/server/CDN caches.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket.
Problem: The client needed to enable automatic translation for post content while disabling it for String Translations in the WPML plugin. Solution: We advised the client to use the Translation Management dashboard (WPML -> Translation Management) to control which content should be translated. Specifically, to disable automatic translation for strings, the client should not select them in the dashboard. For detailed guidance, we recommended reading the Translation Management guide.
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 further assistance is needed, please open a new support ticket.
The client is experiencing an issue where the WPML site key is not working, and there is a message in WP Admin indicating an inability to connect to wpml.org. Despite trying to re-register with both an existing and a new key, the issue persists.
Solution:
We recommend following the steps outlined in a similar case to determine if the same bug is affecting your site. Please visit the following link to try the suggested workaround:
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client is unable to find the option 'Set different slugs in different languages for Product categories' in WPML settings. Solution: We resolved the 404 error on category pages. For issues related to product slugs, we have created a separate support ticket. You can follow the discussion and find a solution on this topic at https://wpml.org/forums/topic/is-it-possible-to-keep-product-slugs-not-translated/. If your 404 error issue is resolved, please mark this ticket as resolved, and we will continue to assist you with the product slug issue in the new ticket.
Please note that the solution provided might be 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 the issue persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
You are trying to edit a link in a button using the Gutenberg editor, but after saving and reloading the page, the URL unexpectedly changes to include '-2'. This issue does not occur when WPML is deactivated.
Solution:
The issue was due to an old entry in the database where the post_name in the wp_posts table was incorrectly set. We corrected this by updating the database entry to the correct post_name. You can apply a similar fix by running the following SQL command in your database:
UPDATE `wp_posts` SET `post_name` = 'desired-post-name' WHERE `wp_posts`.`ID` = your_post_id;
Replace 'desired-post-name' with the correct name of your post and 'your_post_id' with the ID of the post you are updating.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to translate the payment gateway description on your site using WPML, but the translation does not appear on the front-end. Solution: This issue might be due to a compatibility problem. First, ensure you have followed the steps outlined in finding strings that don't appear on the string translation page. If the issue persists, you may need to add language configuration for plugin or theme options strings in WPML >> Settings >> Custom XML Configuration tab. Consider implementing the workaround suggested in these tickets after a full site backup:
After applying these changes, clear all types of caches and check if the issue is resolved.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive