Problem: The client is trying to use the automatic translation feature for pages but cannot find the option in WPML → Translation Management as shown in the tutorial.
Solution: 1. We recommend ensuring that the Automatic Translation Editor is enabled. This is necessary before using the automatic translation feature. 2. Check if you are currently using the Classic Translation Editor and switch to the Automatic Translation Editor if needed. You can find the instructions here: Advanced Translation Editor documentation. 3. If you have the Classic Translation Editor active, you can switch to the Automatic Translation Editor by following this guide: Using the Translation Editor documentation.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us for further assistance.
Problem: Unable to translate acf checkboxes labels.
Solution: 1. Navigate to ACF->Tools and enable the option 'Scan local fields for changes to translation preferences.' and save the changes. 2. Go to WPML->Strings Translations->Auto Register strings for translations and enable the 'Look for strings while pages are rendered' option. 3. Visit the page on the front-end where the string is shown to automatically register strings from that page. 4. Return to WPML->Strings Translations->Auto Register strings for translations and disable the previously enabled options. 5. Search for the strings in WPML->String Translations and translate all instances that appear.
Problem: The client's checkout page is not displaying any content when switching languages. Solution: 1. We recommend going to WooCommerce -> WooCommerce Multilingual -> Settings -> Switching languages when there are items in the cart. 2. Enable the option 'Prompt for a confirmation and reset the cart'. This will display a dialog box that allows users to either proceed and reset the cart or go back and keep the items in the cart. 3. We have also provided a widget called Products before cart reset, which displays a list of products that were removed after switching language or currency. 4. For more information, please read the guide on using this option at the following link: Clearing Cart Contents When Language or Currency Change. 5. Please test this setting on the live site to ensure it resolves the issue.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client has a popup window on their website that is only intended to appear on the Hungarian main page, but it is also appearing on the English main page. Solution: We have identified that the issue arises because Elementor loads the conditions for popups globally, which may include caching, and not directly from the
_elementor_conditions
field. WPML automatically translates the condition IDs, which can cause the popup to appear on all language versions of the page. To resolve this, we recommend the following steps: 1. Install the JSM Show Post Meta plugin. 2. Navigate to the translated Popup edit screen. 3. Click on the "X" icon next to the
_elementor_popup_display_settings
field at the bottom of the page. 4. Save the changes. By removing the
_elementor_popup_display_settings
custom field from the translated popup, the condition for displaying the popup will not be applied to that translation. If you're experiencing this issue and the solution provided does not seem relevant, or if you encounter any other problems, please open a new support ticket with us.
Problem: The client wants to display only the English language on their site and has disabled the French version. However, they have created some products in French and now see a small lock beside the English product fields, preventing them from editing the English version. Solution: 1. If the French content is still present, the client should delete all the French content. For guidance, we recommend following the instructions on how to completely remove a language from the site. 2. Alternatively, the client can: - Re-enable the French language. - Disconnect the English translation from the original French product by selecting that the English page is a translation of 'none'. - Disable the French language again. For more details, see the documentation on how to link already translated pages. The first method will address all translations in bulk, while the second method must be applied to each product individually.
Problem: The client is unable to translate certain elements on their website, including the word 'Recommended' in a sidebar created with the Visual Sidebar Editor plugin for WPBakery Visual Composer, strings from the YARPP plugin for related posts, and the comment section.
Solution: If you're experiencing issues with translating sidebar elements, related posts, or the comment section, we recommend you follow these steps: 1. Ensure you have a backup of your website. 2. Navigate to WPML > Settings > Custom XML Configuration, paste the following code, and save:
3. Go to WPML > Theme and Plugins localization and scan the YARPP plugin. 4. Proceed to WPML > String Translation and translate the strings that were indicated in the screenshot provided by the client.
Following these steps should resolve the translation issues. If this solution doesn't look relevant to your problem, please open a new support ticket with us.
Problem: The client needs to duplicate multiple pages from Simplified Chinese to Traditional Chinese and then manually update the content for each page. Solution: 1. To duplicate individual pages, follow the instructions in the Displaying Untranslated Content on Pages in Secondary Languages documentation. 2. Use the "Copying content" section to duplicate pages but remember to click on the
Translate independently
button for each page to avoid automatic overwriting when the default language is updated. 3. If you need to duplicate many pages, refer to the How to Duplicate Pages and Posts in Bulk section. After bulk duplication, you must press the
Translate independently
button on each translation you modify.
If this solution doesn't look relevant, please open a new support ticket and we will be happy to assist you.
Problem: The client is experiencing issues with saving translations in the Advanced Translation Editor (ATE). They can enter the ATE and pull in new automatic translations, but cannot save them. The 'spinner' icon continues to spin indefinitely after attempting to save translations. This issue does not occur on the staging site, where everything works normally.
Solution: We recommend checking if the issue can be reproduced with the active Redis plugin, as there have been recent issues related to its implementation. If the problem persists, consider testing with the W3 Total Cache plugin, which has a robust Redis implementation.
If this solution does not seem relevant to your situation, please open a new support ticket with us, and we will be happy to assist you further.
The client is experiencing an 'Internal Server Error' when switching languages on their website after updating WPML to version 4.6.8. The issue does not occur in incognito mode. The client attempted a workaround involving the .htaccess file from a WPML errata page(https://wpml.org/errata/htaccess-is-rewritten-with-language-folder/), but it did not resolve the issue. The client discovered that the RewriteBase in the .htaccess file was incorrectly set to RewriteBase /en instead of RewriteBase /, and after correcting this and removing extra brackets, the site worked correctly.
Solution:
1. We recommend increasing the WordPress memory limit to at least 128MB, as per WPML's minimum requirements
2. Perform a full clean of the website's cache, including at the server level, to see if the issue persists.
3. Ensure that the code provided in the WPML errata page is correctly set in the functions.php file of the theme.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us. You can do so by visiting the WPML support forum.
Problem: The client encountered an error message after attempting to update the WPML Multilingual CMS plugin, which resulted in issues with the website translations. Solution: If you're experiencing similar issues after updating the WPML plugin, we recommend the following steps: 1. Create a full backup of your website. 2. Navigate to your site's files via FTP or your hosting file manager, go to
wp-content/plugins/
, and delete the
sitepress-multilingual-cms
folder completely. 3. Download the latest version of the WPML plugin from our downloads page. 4. Go to your WordPress Dashboard, navigate to Plugins > Add New > Upload, and manually install and activate the plugin. Please try these steps and let us know how it goes.
Problem: The client is receiving messages indicating that WPML Multilingual CMS needs to be activated for WPML String Translation to work, and that WPML Media is enabled but not effective without WPML.
Solution: We recommend checking if WPML Multilingual CMS is active on the website when these messages appear.
If you are experiencing similar issue, first we suggest you try:
Download the OTGS installer, re-install it and re-run it. It should download again the WPML plugin/s and than re-installed them.
Problem: The client is experiencing an issue where the Elementor editor loads fine for the default language (English) but gets stuck on the loading screen when trying to edit translations manually.
Solution: First, we recommended the following steps to ensure that the translation is not being hindered by the use of different translation editors: 1) Create a Header Template 2) Duplicate it to secondary languages 3) Switch to a secondary language via the Dashboard language switcher of the top header 4) Open the Duplicated Header Template for edit 5) Click on Translate Independently button 6) Update the Template from Elementor Editor 7) Save the changes For more details, please refer to our documentation on using different translation editors for different pages.
If the issue persists, it may be due to a conflict with the rewrite rules in the .htaccess file. We found that making the following changes to the .htaccess file resolved the issue on a staging site:
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
