Problem: The client is experiencing intermittent issues where pages translated using the WPML AI automatic translation engine are not displaying correctly in the frontend, despite appearing translated in the backend. This issue occurs even though the translation credits are deducted and the pages are set to review mode to prevent publishing unreviewed content.
Solution: We recommend the following steps to address the issue: 1. Ensure that there are no conflicts with security plugins by temporarily disabling them. 2. Use troubleshooting tools provided by WPML to check for any anomalies in the translation process. 3. Attempt re-translating the page with a minor change, such as adding a space to the page title, to force a refresh in the translation process without needing to use the 'overwrite translation' option, which consumes additional credits. 4. If the problem persists, verify the issue using the same admin account that was used for the initial setup or translation.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 continues, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client is experiencing issues with Google indexing and client-side redirections when using WPML's Browser Language Redirect feature. This problem occurs when analyzing Italian pages on their multilingual site, which are being redirected to the English version. Solution: We recommend disabling the Browser Language Redirect feature to resolve the indexing issues and prevent unwanted redirections. You can disable this feature by navigating to WPML → Languages page and locating the Browser language redirect setting. For more detailed instructions and understanding of how this feature impacts Google indexing, please refer to our documentation: How Browser Language Redirect Affects Google Indexing and Automatic Redirect Based on Browser Language.
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 open a new support ticket at WPML support forum.
Problem: The client is working on a site under development and is trying to use WPML with WP All Import. They are facing issues with automating the WPML export and import process, as it requires manual initiation. Solution: We confirmed that the WPML Export & Import add-on does not support automation through cron jobs, webhooks, or custom PHP calls. The import process must be manually triggered. For automating the import process, the client needs to configure WP All Import directly. The WPML add-on only ensures that the multilingual data is correctly structured and mapped during the import. For more details on how to import with WPML Export & Import, please visit WPML Export & Import documentation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to convert their website to multilingual using WPML and is facing an issue where Elementor is not opening. Solution: First, ensure that you are not trying to directly translate the Elementor pages. Instead, follow these steps: 1. Navigate to WPML > Translation Management 2. Select the content you wish to translate. 3. Send it to translation. 4. Go to WPML > Translations and translate the content using the Advanced Translation Editor. If Elementor still does not open, check the WPML language settings. The issue might be due to the Arabic language being set to 'Hidden' in WPML > Languages. To resolve this: 1. Go to Users > Profile and check the "Display hidden languages" checkbox. This should allow Elementor to load properly in the Arabic language.
If these solutions do not resolve your issue or seem 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 the problem persists, please open a new support ticket.
Problem: The client is experiencing a persistent database error related to a missing table 'wp_icl_background_task' while using WPML on their website. Despite attempting to resolve the issue through the WPML troubleshooting page and reinstalling WPML, the error persists, causing white screens (fatal errors). Solution: We recommend the following steps to resolve the issue: 1. If WPML was just activated and there are no translations yet, consider resetting WPML and reconfiguring it. This can often resolve table-related issues. - Go to WPML → Support and click the Troubleshooting link. - In the Reset section, select the 'I am about to reset all translation and language data' checkbox, then click the 'Reset and deactivate WPML' button. Ensure you take a backup first. More details can be found here: WPML Reset Documentation. 2. If the issue persists, check for any custom code in the wp-config file that might be affecting WPML's functionality. Removing problematic lines of code can resolve the issue. 3. Additionally, refer to the WPML errata page for known issues related to missing database tables: Missing WPML Tables Errata.
If these solutions do not resolve the problem or if they seem 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 the issue persists, please open a new support ticket for further assistance.
Problem: The client is concerned about the high usage of translation points for product descriptions that are mostly similar, questioning why translation memory does not recognize these similarities. The client also inquires about earning translation points, refunding points, and deleting translation tasks. Solution: We explained that translation memory requires segments to be identical to match and be reused; even slight differences mean they need to be translated anew. For further details on how WPML tracks translations, visit https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/. Regarding earning points, the client can purchase a credits package or use a pay-as-you-go system. If the client prefers to translate manually, they can assign themselves as the translator via WPML > Translation Management, then go to WPML > Translations to take and translate the page. More information on credits can be found here: https://wpml.org/faq/what-are-credits/. Unfortunately, once translation credits are used, they cannot be refunded as the cost has already been incurred with the third-party translation engine. Additionally, translation tasks cannot be deleted but can be canceled from WPML > Translation Management > Jobs, or reassigned to the client for a new translation attempt.
If this solution does not resolve your issue or 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. For further assistance, you can contact us through the WPML support forum.
Problem: You are working on a site under development and trying to translate WooCommerce product descriptions using WPML. After completing the WooCommerce product translation, the translation queue shows 'in progress', but the product description is not translated successfully and the webpage remains in English. Solution: 1. Disable Object cache and then resend the product for translation from WPML > Translation Management. 2. If the issue persists, ensure that you have sent the product for translation correctly. If the status says 'waiting for translators', it means you or another user needs to go to WPML > Translation, take and translate the job. If you wish to translate automatically, you need to choose that option in translation management.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that the 'add to cart' button on category pages was displaying in Slovenian instead of English, despite being correctly translated in the WPML string translation and displaying correctly in the shop page.
Solution: We suggested the client to first switch to the parent Divi theme from their customized child theme to check if the issue persists, emphasizing the importance of backing up the website and trying this on a staging site first. If the problem continued, we recommended: 1) Rescanning the theme, WooCommerce, and any other relevant plugins to check for untranslated strings. 2) Deactivating all plugins except for WPML, String Translation, WCML, and WooCommerce, and then switching to a standard theme like 2024 or 2021 to isolate the issue. 3) Reactivating plugins one by one to identify any conflicts, and then switching back to the original theme to see if it causes the issue.
If these steps do not resolve the issue or if they seem outdated or irrelevant to your current setup, 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 the problem persists, please open a new support ticket.
Problem: The client was experiencing an issue where Kadence Dynamic Links on translated pages were still pointing to the main language version, despite the pages being fully translated using WPML's automatic translation feature.
Solution: We recommended two main adjustments to resolve this issue: In the same WPML -> Language section, under 'Make themes work multilingual', the 'Adjust IDs for multilingual functionality' option was not selected. Selecting this and saving the settings should ensure that dynamic links automatically update to the correct language version.
If these steps do not resolve your issue, or if the solution seems 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 problem persists, please open a new support ticket.
Problem: The client reported an issue where the main shop-page in English displayed prices in euros instead of dollars when viewed from the US, and the single product page showed prices only in euros. This discrepancy occurred despite using WooCommerce Multilingual & Multicurrency with geolocation-based currency settings. Solution: We initially suggested checking if the issue was related to caching, either via the website cache or the browser cache. After further investigation and testing with a VPN set to the US, it appeared that clearing the cache resolved the issue. We recommended the client to continue monitoring the situation and to clear the cache regularly to prevent similar issues. Additionally, we advised setting up the site in a minimal environment to check for any conflicts with themes or plugins if the problem reoccurred. This involves switching to a default WordPress theme and deactivating all plugins except for WPML, its add-ons, and WooCommerce. If the issue persists, the client should activate plugins one by one to identify the problematic plugin.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing a 404 error when switching to the Hungarian language for a product category URL on your site, it might be due to incomplete translations in the WPML settings. Solution: We recommend you try the following steps: 1. Navigate to WPML → Taxonomy Translation → Product Categories. 2. Check if all fields are properly filled in for Translations of taxonomy Category labels and slug, including the Plural translation field. 3. If any fields are empty, please complete the missing translations. After completing these steps, please verify if the issue persists. For more details, you can check the related known issue at https://wpml.org/errata/product-category-links-do-not-use-translated-slugs/.
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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are translating a Divi theme builder template for a WooCommerce category from Spanish to Catalan using WPML. After completing the translation, accessing the translated page via the translation menu results in a 'not found' error. Solution: Ensure that you have translated all the products that should appear in that category. If the products are not translated, WordPress might consider the category as empty, and thus, the category archive will not exist. If you're experiencing this issue, we recommend you check and translate all related products.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and verify the version of the permanent fix. Ensure you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: You are trying to translate a custom filter message on the WooCommerce thank you page, which is not visible in WPML string translation. The message is added via a filter in the functions.php file of your child theme.
Solution: To make your custom messages translatable, you need to wrap all static texts in gettext calls such as
__()
and
_e()
, specifying a text domain. Here’s how you can modify your code:
$thank_you_msg = __('Status: Order Completed & Paid!', 'your-text-domain') . '<br /><br />' . __('You are all set! You can now close this tab and head over to your email inbox for all the details about your challenge.', 'your-text-domain');
After modifying the code, go to WPML → Theme and plugins localization and scan your child theme for new strings. This will register them in WPML’s String Translation, where you can provide translations. For more details on adding gettext calls and scanning themes, visit Adding GetText Calls to PHP Code and Scanning a Theme or Plugin to Update Existing Translations.
Ensure you are properly loading the text domain in your theme. For guidance, see load_theme_textdomain and Text Domain. Always back up your database before making changes.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum.
Problem: The client is using the WP Go Maps plugin and is unable to find the category strings for translating country names using WPML. Despite rescanning the plugin and following existing threads, the issue persisted. Solution: We discovered that the WP Go Maps plugin does not natively support the translation of marker categories. However, a workaround is available: 1. Edit the plugin file at
. 3. Enable WPML’s “Look for strings while pages are rendered” setting found in the “Auto register strings for translation” block (WPML -> String Translations). After these steps, you should be able to search for your category name in WPML and add the respective translations. For more details, visit WP Go Maps forum.
If this solution does not resolve your issue or 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. If needed, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was facing an issue where the corresponding language version of an article, written by a Contributor and published by the site administrator, wasn't appearing on the front end of the website. Solution: We advised the client to check the status of the post in the backend. It was discovered that the post was in a 'pending' status because it was translated by a Contributor who does not have the permission to publish. We changed the language to Indonesian from the top admin language bar, selected the 'edit anyway' option, and changed the status from pending to published. This resolved the issue, and the post now appears correctly on the front end. We recommend avoiding the use of the Contributor role for translations and suggest using at least an Editor role.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket 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
