Problem: You are setting up a multilingual and multicurrency e-shop using WPML and have encountered a message about potential caching issues that might affect currency display for customers. Solution: If you're experiencing this, we recommend checking if your current setup with Lightspeed is functioning correctly. If you encounter issues, add the following cookies to your cache exclusion list:
wcml_client_currency
wcml_client_currency_language
wcml_client_country
If this does not resolve the issue, consider also adding WooCommerce pages to the exclusion list. Regarding the setup of language and currency versions, it is your decision whether to place them on separate domains or in folders.
Please note that this solution might be 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues with Contact Form 7 on your translated event page using WPML, built with Gutenberg and Kadence blocks pro. Specifically, dropdown fields in Contact Form 7 are not displaying correctly, the edit screen doesn't load properly, ACF Pro fields are missing on the translated page, and new translations are not appearing in the translation queue. Solution: We recommend trying the steps outlined in this forum post: WPML Multilingual CMS & Contact Form 7. Additionally, a permanent fix is expected in the next version of Contact Form 7 Multilingual, version 1.3.2. Although we do not have an exact release date, it is anticipated to be available soon.
Please note that this solution might be 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. If the issue persists, please open a new support ticket.
Problem: The client has a custom post type called Projects, and the images are not syncing across translations. Solution: 1. Verify if the images are added through a custom field. If so, ensure the custom field is set to "copy" in the translation settings. 2. If the images are not added through a custom field, navigate to WPML->Settings->Media Translation and run the function that duplicates or translates images to other languages. 3. If the issue persists, check the widget, block, or custom field used for these images. Since they are set through Elementor, without backend access, further specific guidance cannot be provided. 4. Change the translation preference of the custom fields to "copy" using the Expert mode. Then, make a small edit to the content of the project so WPML can detect the changes and retranslate, which will copy those fields in other languages.
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 at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing several issues while translating pages on their website. These include incorrect page display with archive categories opening on the right, corrupted CSS settings after translation, inaccurate translations, and a 500 internal error when translating the home page. Solution: 1. For the issue of archive categories appearing on the right and corrupted CSS, we recommend editing the English language page by selecting the "No Sidebar" option in the page settings. This can be done by navigating to the page edit section in the admin panel. 2. To address the 500 internal error during homepage translation, we suggest enabling the debug log on your server to identify the cause. You can find instructions on how to do this here: Debugging in WordPress. 3. If you encounter a 'Request Timeout' error, please contact your hosting provider to increase the server resources, which should help prevent this issue.
Please note that this solution might be 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. If the problem persists, please open a new support ticket.
Problem: You have mistakenly set Russian as the default language in WPML on your website and are unable to translate content from English to Russian as a result. Solution: If you're experiencing this issue, we recommend the following steps to reset WPML and set English as your default language: 1. Backup your website. 2. Navigate to WPML → Support and click on the Troubleshooting link. 3. On the Troubleshooting page, in the Reset section, check the box that says
I am about to reset all translation and language data
. Then, click on the
Reset and deactivate WPML
button. 4. Reactivate WPML and set it up again, this time ensuring English is set as the default 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: The client is unable to see or use the 10000 translation credits assigned to their site, and they cannot assign credits under the 'Tools' tab. Solution: If you're experiencing issues with not seeing or being able to use assigned translation credits, we recommend the following steps: 1. Visit your WPML account page and ensure your site is listed under the 'Sites Using Prepaid Credits' section. 2. Perform a full site backup. This step is mandatory. 3. Follow these steps to register your site with a new key: - Navigate to your account page and delete the existing key for your site. - Go to Plugins > Add New > Commercial tab on your site's dashboard. - Click on 'Unregister WPML from this site' and refresh the page. - Click on 'Get a key for this site' and copy the newly generated code. - Return to Plugins > Add New > Commercial tab and register the site with the new key. For more detailed instructions, please refer to our documentation on why credits may be missing and how to fix it and how to install WPML.
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, 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.
Problem: You have a shop set up in Danish and have translated the shop page to English using WPML. While the shop page displays prices and categories correctly, the product titles appear in Danish instead of English. However, clicking on a product displays it in the correct language. Solution: First, ensure that your WPML and other related plugins are up to date. You can do this by navigating to your WordPress admin area, going to
wp-admin/plugin-install.php?tab=commercial
, and clicking on "Check for updates". After updating, verify if the issue persists. Next, check if the products showing Danish titles are drafts. If they are, you need to publish these products and ensure that their titles are translated correctly into English.
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 problems continue, please open a new support ticket.
Problem: The client wants to set up WPML so that all languages, including the default, are in subdirectories without creating a root page for the site. Solution: We recommend setting an empty root page with a specific PHP template to automatically redirect visitors to the default language directory. This approach prevents both URLs (domain.com and domain.com/uk) from being accessible simultaneously and avoids duplicate content issues with Google. Here are the steps to implement this: 1. Select "Edit root page" and create an empty WordPress Page. 2. Follow the instructions to create a PHP template with the redirect. 3. Assign the template to your empty root page. For detailed guidance, refer to the section "Redirecting the Root Domain to the Default Language Directory" in our documentation here.
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 here.
Problem: If you're experiencing issues with translating the string "Recently Viewed Products" in the Astra theme or its addon plugin, follow these steps. Solution: First, navigate to WPML > Theme and plugins localization and select 'Scan strings in the theme and plugins'. After scanning, go to WPML > String Translation and search for the strings you need to translate. If you can't find the string "Recently Viewed Products", ensure you are searching under the domain "astra-addon". Once you find the string, translate it accordingly. For more detailed guidance, refer to our documentation on finding strings that don't appear on the String Translation page.
If this solution does not resolve your issue or seems 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 need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing a critical error (white page) when editing a post with WPML activated, and WPML indicates that the REST API is not activated even though it is working, the issue might be related to the ACF Multilingual plugin. Solution: We recommend reinstalling the ACF Multilingual plugin with a fresh copy. You can download it from here.
If this solution does not apply to your case, or if it seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: The client was experiencing an issue where clicking the Slovak flag on their website redirected to an incorrect URL instead of switching back to the Slovak version of the site. Solution: We recommended the following steps to diagnose and potentially resolve the issue: 1. Clear Cache: We advised clearing WPML’s internal cache from WPML > Support > Troubleshooting > Clear the cache in WPML, disabling the Language Switcher Cache, clearing any site caching plugins, and the CDN cache if applicable. 2. Use Footer Language Switcher: We suggested activating a footer language switcher from WPML > Languages to check if the issue persists with a different switcher setup. 3. Test in Minimal Environment: We recommended deactivating all plugins except WPML CMS and switching temporarily to a default WordPress theme like Twenty Twenty-one to see if the issue still occurs. This helps in identifying any conflicts with other plugins or themes.
Ultimately, the client discovered that the issue was caused by incorrect custom codes provided by their hosting service for redirecting www/non-www URLs in the wp-config file. Removing these codes resolved the problem.
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.
Problem: The client updated WordPress to version 6.7 and all WPML plugins to the latest versions. However, they encountered an issue where they could not switch the frontend language to German (DE) by clicking on the DE flag in the main menu. The domain for the German language was incorrectly redirecting to the main domain. Solution: We first ensured that the client was using the latest WPML version by advising them to update their WPML plugin and add-ons to version 4.6.14. We then guided the client to check their domain and 'A different domain per language' setup according to our guide. Further troubleshooting steps included: - Synchronizing posts taxonomies - Clearing the cache in WPML - Resaving the permalink structure Upon deeper investigation, it was found that the issue was due to a server-level redirection, likely configured in the LiteSpeed server settings or the hosting control panel. We recommended checking the LiteSpeed server configuration, hosting control panel redirects, and DNS settings for the domain. If these steps do not resolve the issue, we advised contacting the hosting provider for further assistance.
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing a JavaScript error 'TypeError: Cannot read properties of undefined (reading 'indexOf')' while editing a custom field in their WordPress site using WPML and ACF. Solution: 1. We recommend confirming if the issue persists when only WPML plugins and ACF are active, with all other plugins and custom code disabled. 2. If the problem continues, provide a staging site for further investigation. Ensure to back up your site before making any changes. 3. Consider checking if the issue might be related to the browser, device, user, or location used for accessing the site. 4. Ensure that ACF field groups translation settings are set as not translatable to avoid issues. More details can be found here: Advanced Custom Fields field group should be set as not translatable.
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. For further assistance, please open a new support ticket.
Problem: You are trying to update a photo on the English version of a page, but the changes are not reflecting, and the page displays an incorrect image. The correct version appears on the Indonesian page. Solution: First, verify the default language in which the product was created. If English is the default language, you should be able to edit and change the image directly in the English admin. If Indonesian is the default language, you will need to use the WPML Media addon to manage and synchronize media for translations. Detailed guidance on using this addon can be found in our documentation: WPML Media Translation.
If this solution does not apply because it might be outdated or not suitable for your specific case, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You are using WPML and want to understand how translations are affected when you modify the original source content after modifying a translation, including changes like images or alignment. Solution: When you modify the source content, we will ask you to translate the segment again, as there won't be a matching segment in your Translation Memory. The translated sentences in the Advanced Translation Editor are saved to the translation memory and will not be translated automatically again. For more details on how WPML tracks your translations, we recommend reading our documentation here: https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/.
If this solution does not apply to your case, or if it seems outdated, please open 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
