Problem: You are working on a site under development and trying to translate Elementor buttons using WPML, but the buttons are not translating. Solution: First, ensure you are following the correct procedure to translate Elementor buttons. We recommend checking our guide on How to Translate an Elementor Website with WPML. Additionally, we have enabled debug information for this support ticket. Please follow the instructions on how to retrieve this information from your site and provide it to us, so we can assist you further.
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.
Problem: You are experiencing intermittent 404 errors on course pages when using WPML with Tutor LMS. Solution: We recommend updating your Tutor LMS to version 3.9.2 as the Tutor LMS team has recently resolved this issue and released an update. This should fix the intermittent 404 errors on your course pages.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is using WPML with a custom theme (Nexis) and Elementor on their website. They are facing issues with language flags not displaying correctly on the Home and Contact pages in the German version and missing on all English pages. The flags appear correctly on other pages like 'Services' or 'Recruiting'. The sticky header displays the flags as expected. Solution: We recommended ensuring that the header templates used for the homepage or the contact page are fully translated. We advised following the method outlined in the WPML documentation for Elementor compatibility, which can be found here: https://wpml.org/documentation/plugins-compatibility/elementor/.
If this solution does not resolve the 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 persist, please do not hesitate to open a new support ticket for further assistance at our support forum.
Problem: The client is experiencing an issue where, after completing a checkout on their WooCommerce site with the WPML Multilingual CMS plugin activated, an error message appears, and the user is not redirected to the 'Thank You' page. However, the order is placed successfully, and the confirmation email is received. The issue does not occur when the WPML plugin is deactivated. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Confirm that all WPML and WooCommerce plugins, as well as your theme, are updated to their latest versions. 2. If the issue persists after updates, disable all plugins except for WPML and WooCommerce to check if the issue still occurs. 3. Test the checkout process with a new product. 4. Enable WordPress debugging to identify any specific errors related to WPML. To do this: - Edit the
wp-config.php
file and add the following lines before the comment '/* That's all, stop editing! Happy publishing. */':
file in the /wp-content/ directory for any WPML-related errors. 5. Share the full error message from the debug log with us for further analysis.
If these steps do not resolve the issue, or if the solution 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: The client was unable to display all available languages in the WPML language switcher on English pages, which is the default language. Despite enabling settings like 'Use directory for default language' and 'Always show languages (even if not translated)', and performing actions such as clearing WPML caches and re-saving permalinks, only English was displayed in the switcher. Additionally, the Menu Sync tool was returning a 500 error. Solution: We resolved the issue with the language switcher not displaying all languages by clearing the cache at the hosting provider, Kinsta. This action allowed the switcher to appear correctly in English. For the 500 error with the Menu Sync tool, we recommend checking server error logs for more details or increasing the PHP memory limit, as it might be related to server resource limits.
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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: The client reported that the white menu appears over the slideshow on the original website. Solution: We suggested deactivating the PixelYourSite PRO and Seraphinite Accelerator (Full, premium) plugins temporarily to check if they are causing the issue. Additionally, we requested temporary access (wp-admin and FTP) to the site—preferably to a test site where the problem has been replicated—to provide better assistance.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After migrating a website from one server to another, the layout is damaged, and a PHP fatal error related to the WPML plugin occurs. The error message indicates an issue with
DOMDocument::loadHTML()
being called with an empty argument. Solution: 1. Manually upload fresh copies of the WPML plugins from your account at https://wpml.org/account/downloads/. 2. Temporarily disable all plugins except for the WPML plugin to check if the issue still occurs. 3. If the problem persists, provide temporary access (wp-admin and FTP) to a staging or test site where the problem can be replicated. Include exact steps to replicate the issue for more efficient investigation.
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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is using WPML with a theme called Digicove and Elementor, but only the page titles are being translated automatically. The rest of the page content, including custom Elementor widgets, is not being translated. Solution: We identified that the theme and its custom Elementor widgets were not officially compatible with WPML, which caused the translation issues. To resolve this, we recommended registering the custom Elementor widgets for translation following the guide at https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/#register-custom-elementor-widget-for-translation. We assisted the client by manually configuring and translating a few pages to demonstrate the process. We advised the client to re-save and re-translate other pages to see if any widget still needed to be added.
Please note that this solution might be outdated or not applicable to your case. If you're experiencing similar issues, 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: The client was unable to load the AI Translation section in WPML and could not map the default language, German, to a supported language for automatic translation. The 'Map language' button showed no options, and the Language Mapping column was not displayed. Solution: 1. **Increase the WordPress Memory Limit**: The client was advised to increase the memory limit to at least 128MB, ideally 256MB, by modifying the
wp-config.php
file. 2. **Clear WPML's Cache**: The client was instructed to clear WPML's internal cache through WPML → Support → Troubleshooting. 3. **Update AI Translation Settings**: After increasing the memory limit and clearing the cache, the client needed to check the AI Translation settings in WPML → Settings to ensure the system could properly display mapping options.
If the solution provided 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 WPML Support Forum.
Problem: The client is unable to see the content designed with Divi Builder when attempting to translate a page using WPML. Only the page title appears, and changing custom field translations only displays the code names of the content. Solution: 1. Edit the Default Language Page: * Navigate to the original page in the default language and edit it using the Classic Editor to ensure all elements are recognized. 2. Trigger a Page Update: * Make a minor temporary change, like adding a space in the page title, and update the page. 3. Revert the Temporary Change: * Remove the temporary change and update the page again. This forces a re-scan of the content. 4. Confirm Custom Field Settings: * Check under WPML → Settings and ensure all fields starting with '_et_pb_' are set to 'Translate'. Save any changes. 5. Clear WPML Cache: * Go to WPML → Support and click on 'Troubleshooting'. Then, clear the cache in WPML. 6. Attempt Translation Again: * Try translating the page again by clicking the plus icon next to your target language.
If these steps do not resolve the issue, it may be due to other factors or the solution might be 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 requested a credit refund for their site, noting discrepancies in credit usage for DeepL and PTC, with a total request of 275,000 credits. Solution: We refunded the 200k credits as requested. However, we advised the client that ongoing translations use the engine selected at the time of sending the translation. For future instances, if the same text is translated and stored in the translation memory, it should apply to other products. However, to ensure the translation memory is applied correctly, it's recommended to send products for translation in smaller batches.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if there's a permanent fix available. Ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket at our support forum.
Problem: The client is experiencing issues with custom widgets turning into 'Missing widget' entries after saving a page in SiteOrigin Page Builder, following updates to WPML v4.8.4 and String Translation v3.4.1. Additionally, there is a 404 error on the pagination of a custom post type archive, which temporarily resolves upon re-saving the ACF custom post type but reappears later.
Solution: We have determined that the issue with the widgets is not directly caused by WPML or String Translation, but rather by how the custom widgets are loaded and registered. Ensure that all custom widgets are registered using the standard
widgets_init
action and confirm that widget IDs and class names exactly match those saved in SiteOrigin. Also, check for PHP 8.3 compatibility as the plugin might use outdated code.
For the 'Missing widget' issue, disabling the 'Automatically detect best options for translating image texts' setting under WPML → Settings → Media Translation might resolve the issue. This is because WPML's media duplication process could be stripping necessary backslashes from the widget's data when saved in a secondary language. If problems persist, it's recommended to use
wp_slash()
when saving data to ensure backslashes are preserved.
If these solutions do not resolve the issues or if new problems arise, we recommend opening a new support ticket. Additionally, it's advisable to 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 at WPML Support Forum.
Problem: The client is experiencing issues with translating LearnDash courses using WPML on a site using the Kadence theme with Gutenberg. Specifically, when translating courses, the English versions lose their assigned lessons/topics/quizzes after saving, creating duplicate lessons and displaying 'trashed' lesson URLs in the Advanced Translation Editor. The course builder also reverts to an empty state, and the internal structure is lost on every save. Solution: We found that the client had not followed the correct procedures for translating LearnDash courses with WPML. Here are the steps to correctly translate LearnDash elements: 1. Ensure that lessons and quizzes are added in the builder tab for the translated courses. 2. Manually translate questions and add answers directly in the translated question screens. 3. Use the Translation Dashboard of WPML with the Advanced Translation Editor to translate courses, lessons, quizzes, and questions. For more details, refer to our guide on translating answers and building courses. Note that trashed lessons and quizzes appearing is a LeanDash behavior and not related to WPML. If you do not want these items to appear, they must be permanently deleted from the trash section.
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 also visit our support forum at WPML support forum.
Problem: The client is unable to see the option to change the language to English on some pages of their website. Solution: If you're experiencing a similar issue where the language switcher is not appearing on some pages, we recommend checking if this issue has been previously discussed in a related support thread. You can continue the discussion there if it's the same issue. Here is the link to a possibly related discussion: https://wpml.org/forums/topic/lack-of-language-translation-option-in-the-new-format/ If your issue is different, please provide more details about the missing language switcher, including a screenshot that illustrates the problem. This will help us understand and address your issue more effectively.
Please note that the solution provided might be outdated or not applicable to your specific case. We highly recommend checking the 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, do not hesitate to open a new support ticket. For further assistance, you can also visit our support forum: https://wpml.org/forums/
Problem: The client reported a fatal error involving WPML and Elementor Pro plugins, which prevented Elementor from loading correctly. Additionally, there were issues with missing images on the website, specifically on the front page, which seemed to affect the slider's functionality. Solution: We clarified that the fatal error the client mentioned was related to Elementor and occurred even when WPML was disabled, indicating that it was not a WPML issue. We advised the client to contact Elementor's support team for a resolution regarding the error. For the missing images, it was noted that they had been deleted from the server, which the client was addressing by re-uploading them.
If this solution does not resolve your issue, 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. 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
