Problem: The client reported multiple issues: an error indicating that the site does not meet WPML's minimum requirements, mismatches in the number of products in categories, a missing price filter in different language versions on various devices, and untranslated footer information in the Lithuanian version of the site. Solution: For the untranslated footer using Elementor, we recommend making a minor change in the default language version of the Elementor template and then re-translating it. This approach was tested successfully on a staging site. Additionally, ensure to clear your browser's cache to see the changes. If you're experiencing similar issues, we recommend checking for any discrepancies in product categories and ensuring that all elements are correctly translated and displayed across different languages and devices. It's also crucial to verify that your site meets the minimum requirements for WPML.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related 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 reported multiple issues after noticing an error about the site not meeting WPML's minimum requirements, which later disappeared without any action taken by the client. The issues included mismatches in product counts across categories, the price filter not being visible or functioning correctly across different languages and views, and untranslated address information in the footer. Solution: We examined the mismatch in product counts within categories. It was found that the content and products were initially created in English and then translated, with English being the default language. The primary issue was with the products in the default language not being assigned to the correct categories. We recommend the client to review all products in the default language to ensure they are correctly categorized. This should be done with WPML disabled to confirm that the setup works independently of WPML. Once verified, WPML can be re-enabled to check if the translation issues persist. If problems continue, we advise opening a new support ticket.
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 issues persist, please do not hesitate to contact us by opening a new support ticket at WPML support forum.
Problem: The client reported that WPML was not fully installed on their second website, which was necessary for testing the carousel Media Translate feature. Solution: We checked the installation status and updated it accordingly. After the update, we confirmed that the issue was related to a validation problem, which we resolved. If you're experiencing similar issues, we recommend verifying that WPML is fully installed and functioning correctly on your site.
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 for further assistance.
Problem: After the last update, the website became very slow. Disabling the WPML plugins temporarily resolved the issue, but reactivating them triggered an error related to WP Endpoints and database entries. Solution: If you're experiencing this issue, it might be due to one of two reasons: either WPML was previously used and reset, or the database prefix changed. We recommend trying the workaround provided in the following errata. Please ensure that WPML is enabled when applying this workaround. If this does not resolve the issue, or if you need assistance with the workaround, do not hesitate to contact us.
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 using the Advanced Translation Editor to translate pages, but even after translations are 100% completed, they still show as 'In Progress'. Consequently, these pages are not available on the frontend. Solution: First, please try accessing your page again to see if the issue persists. If it does, follow these steps: 1. Navigate to your site's WPML > Support > Troubleshooting page. 2. Locate the section labeled 'Your Automatic Translation account id is' and copy the values, which are separated by a pound sign (#). 3. Provide us with this number so we can confirm if the issue is the same as previously identified on another site. If these steps do not resolve the issue or if it appears on your production site as well, we may need direct access to apply a fix. In such cases, we would install a small plugin specifically for troubleshooting purposes.
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: The client was experiencing layout issues when switching languages on their website, which could be due to theme compatibility or incorrect language settings. Solution: 1. Verify the correct language assignment for affected pages in the WordPress admin. 2. Temporarily switch to a default WordPress theme like Twenty Twenty-Three to check if the issue persists, indicating a theme-related problem. 3. Clear all caches to ensure changes take effect. 4. Update all WPML plugins, the site theme, and other plugins to their latest versions. 5. If the issue persists, consider advanced troubleshooting such as custom CSS or page builder configurations.
Problem: The client is facing an issue where the 'Mega Menu' is visible in the English version of their website but disappears when switching to other languages. Solution: We recommend the following steps to address the issue: 1. Ensure that the 'Mega Menu' is properly configured in the original language (English). 2. Verify that all translations for the 'Mega Menu' are complete and accurate in each language. 3. Check that the theme and WPML settings are correctly configured to display the menu in all languages. If these steps do not resolve the issue, or if the solution 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to have text editor widget links automatically update to the correct language path during page duplication, but the URL paths are not updating as expected. Instead of showing the en-au version, the links are defaulting to the English version. Solution: We recommend converting the duplicated page into a translation to ensure that the links update to the correct language path. You can find detailed instructions on how to do this in our documentation: Convert a Duplicate Into a Translation.
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are using WPML with Elementor Pro, WooCommerce, and Bookings for WooCommerce on your website and are trying to translate a single booking product page. However, the date picker is not visible on the translated page, which prevents service purchases. Solution: We have identified that this issue has been resolved in the latest versions of the Bookings for WooCommerce plugin. The plugin's author has included a fix in the recent update. Here are the details from the plugin's change log:
3.10.1 – Released on 28 November 2025<br />New: Latest compatibility With WP[6.8.3] and WC[10.3.5].<br />New: Compatibility with WPML
We recommend updating the Bookings for WooCommerce plugin to the latest version to resolve this issue.
If this solution does not apply to your case, or if it seems outdated, we encourage you to 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You are using the Real Homes theme and have created a search form with Elementor. Although you have translated the Property Features taxonomies using WPML, the translated features are not displaying in the Elementor search form, except for one feature that remains untranslated and in English. Solution: We tested the issue by setting up a new test site with the Real Homes theme and its plugins. After translating a property and its taxonomies, we added the "RH: Search Form 2" widget on a translated page. The form displayed all features correctly in the translated language. It appears that the "RH: Search Form 2" widget does allow using Real Homes Templates, which are set up in the Customizer's search settings. If you use such a template, you might run into unexpected issues. We were sadly not able to replicate and investigate this issue, as we would require a license key for Real Homes for this purpose. We recommend using the widget without any templates, in case you run into unexpected issues.
If this solution does not resolve your issue or seems outdated, we recommend checking the related 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 is experiencing issues with the 'YITH WooCommerce Dynamic Pricing & Discounts Premium' plugin when using the multicurrency feature of WPML. Specifically, the free gift popup does not add the product with the correct price in different currencies, and sometimes the product is not added to the cart at all. Solution: UPDATE: This issue was solved in YITH WooCommerce Dynamic Pricing & Discounts Premium 4.26.0.
1. We suggested that the issue might be due to the plugin not recognizing WPML/WCML currencies and offered a WPML test site to replicate and address the issue. 2. We provided a workaround involving a code snippet to be added to the functions.php file of a Child Theme or a Code Snippet plugin. The code snippet is available at https://wpml.org/errata/yith-woocommerce-dynamic-pricing-discounts-premium-gifts-not-added-and-currency-switch-fails-on-ajax-requests/. 3. We recommended saving YITH rules only in the site's default language and checking WPML > String Translation for any incorrectly translated strings that might affect functionality.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with taxonomy translation in WPML, specifically with two categories ('oponki' and 'pączki') both translated to 'Donuts' causing conflicts. The client suspected a strange character in the translation fields or a possible duplicate category issue. Solution: 1. We suggested checking the WPML settings to ensure that the 'Copy taxonomy to translations' option is disabled under WPML > Settings > Synchronization of Posts and Pages. 2. We recommended creating a staging environment to isolate the issue by deactivating unrelated plugins and switching to a default theme if necessary. 3. To address the specific issue of duplicate categories, the client can delete the problematic category translations by navigating to Posts > Categories, using the language filter to access translated categories, and deleting them. This action should also remove the translations in WPML > Taxonomy Translation.
If this solution does not resolve your issue or 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 encountering numerous 'Deprecated' error notices across various WPML files when using a recent PHP version (likely 8.1 or higher). These notices indicate that certain PHP functions need updating to comply with newer PHP standards.
Solution: 1. We recommend updating all WPML components to their latest versions via the Plugins > Commercial tab. 2. To hide deprecated and warning notices, adjust the
WP_DEBUG_DISPLAY
and related constants in your
wp-config.php
file. 3. Understand that these PHP deprecation notices do not impact your site's functionality and can be safely hidden in a production environment. 4. For an official update or timeline on when all deprecated code will be addressed, only a WPML specialist can provide this information. We do not have a specific timeline or roadmap available currently. 5. Check your PHP version through WordPress Site Health to ensure compatibility.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and confirm you have the latest versions of themes and plugins installed. If needed, do not hesitate to open a new support ticket for further assistance.
Problem: The client reported that the Bricks Builder blog template layout was not displaying correctly in translated versions, despite multiple updates to the translation. The issue persisted even after creating separate templates for each language and manually connecting them. Solution: We investigated the issue and found that it was related to the translation settings in WPML. Specifically, the settings under WPML > Settings > Custom Field Translation had been modified. To resolve the issue, we recommend: 1. Reverting the translation settings to match those on our sandbox site. 2. Resaving the original template and its translations. Please ensure to back up your site before making these changes.
If this solution does not resolve your issue or 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 using LightspeedHQ to manage stocks between their physical store and WooCommerce webshop, which has been translated into English and German using WPML. They noticed that orders placed on the translated versions of the site are not being synced to the LightspeedHQ system. This issue arises because WPML creates duplicates of products for each translation, each with different product IDs, which LightspeedHQ does not support. Solution: We suggested verifying the REST API responses from the client's website to ensure they are correct and can be retrieved properly in both languages. We recommended exploring the use of a dedicated plugin that supports WPML and can handle translated products. Two potential plugins to consider are:
If these plugins do not resolve the issue, we advised checking with the plugin authors to confirm whether their solutions support the needed functionality and how they process the data. Additionally, we confirmed that WPML's behavior of creating new product IDs for translations is standard and cannot be adjusted.
If this solution does not apply or is outdated, we recommend opening a new support ticket. We also highly suggest 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
