Problem: You are developing a WooCommerce store and have created a staging website to upload a large number of products. You have successfully uploaded products for both the 'Global' and Swedish pages and can see the products and their translations. However, when you go to the Swedish store and select a product category, the page loads with 'Nothing found'. This issue does not occur on the Global page. The post card archives are not working on the Swedish page. Solution: 1) We recommend that you follow this guide when importing your content. 2) To prepare the files correctly before importing the products, please check this guide.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the 'Translation Tools' tab in WordPress does not display properly, showing signs of CSS not loading and a malformed URL causing a 404 error when trying to load a CSS file. Solution: We recommend the following steps to resolve the issue: 1. Perform a full backup of your WordPress site. 2. Disable all plugins except those related to WPML from your WordPress Dashboard > Plugins, and check if the issue resolves. If the issue disappears, reactivate each plugin one at a time to identify the conflicting plugin. 3. Temporarily switch to a default WordPress theme, such as 'TwentySeventeen', via your WordPress Dashboard > Appearance > Themes, to see if the issue persists. If these steps do not resolve the issue, it may be necessary for us to take a closer look at your site. In this case, we would require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated. Please ensure to back up your site using tools like UpdraftPlus.
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 issue persists, please open a new support ticket.
Problem: If you're experiencing issues with assigning translators to translation jobs in WPML and encountering errors, it might be due to restrictions set by your hosting provider on your database user or blocked connections to WPML-related domains. Solution: We recommend checking with your hosting provider to ensure that your database user does not have any restrictions, particularly with commands like
ALTER
. Also, verify that connections to wpml.org and ate.wpml.org are not being blocked. Once these issues are resolved, the translation functionality should work correctly.
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 at WPML support forum for further assistance.
Problem: You are working on translating a website into multiple languages using WPML and facing three issues: 1. A post is stuck during translation. 2. The logo does not appear in the header navigation for languages other than English. 3. Texts from tables on specific pages are not translated into other languages. Solution: 1. The stuck post translation job was unassigned, and we canceled it to resolve the issue. 2. For the logo not appearing in other languages, it was not translated in WPML-> Media Translation. We have now translated it. Please verify the logo in the header across all languages. 3. To translate texts from tables that are added as HTML and not automatically translated in ATE, follow these steps: - Edit the page in the default language. - From the language side panel, click the pencil icon to open the translation editor. - Search for any word in the table. - You will see the table in the HTML field. - Translate it and save the translation.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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 visit our support forum at WPML Support Forum.
Problem: After installing WPML and trying to translate a site using The Gem theme and Elementor, the client is experiencing issues where the homepage appears almost empty, and pages, posts, and categories have disappeared from the backend. The menu on the front end is also non-functional. Solution: We recommend checking if the pages are missing language information. You can do this by navigating to WPML → Support → Troubleshooting and clicking on the option "Set language information". If the problem continues, 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 by visiting http://wpml.org/faq/provide-debug-information-faster-support/.
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: The client added a new Italian language to their WPML setup, but after saving the domain 'flamula.it' in WPML > Languages, it unexpectedly changes to 'it.flamula.si' upon refreshing the page. Solution: 1. Ensure WPML is Up to Date: Verify that all WPML components, particularly WPML Multilingual CMS and WPML String Translation, are updated to the latest versions. 2. Verify Hosting Configuration for 'flamula.it': Contact the hosting provider to ensure that 'flamula.it' is correctly set up as an alias or parked domain that points directly to the main WordPress site without redirection. 3. Re-enter the domain in WPML settings and ensure the Language URL format is correctly set. 4. Clear all caches (plugin, server, browser) and retest the setup. If these steps do not resolve the issue, it might be due to outdated information or a unique case not covered here. 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: You are trying to enable translators to translate content into any language using WPML, but encounter an issue when attempting to translate posts. Specifically, translation engines have stopped working, displaying an 'Authentication error, please contact your translation manager to verify your subscription' message. This error appears in different languages each time you try to translate a post, and clicking 'Take and translate' keeps you on the translations queue page instead of proceeding to the post translation page. Solution: We recommend following these steps to address the issue: 1. Ensure that you are logged into wpml.org. 2. Create a staging version of your website to test if the problem persists in a minimal setup. This approach helps in troubleshooting without the risk of affecting the live website. 3. If the issue still occurs on the staging site, please provide us with the URL and user/password of the staging website. You can set your next reply as private for security.
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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is migrating a user database from Ultimate Memberships Pro to WordPress User Management and needs to ensure that custom field value strings are correctly assigned to the new domain in WPML for proper translation in both English and French. Solution: 1. Correct a typo in the plugin code:
Then, go to "Users > Custom fields" and edit at least one option from the multiselect field. Afterward, translate all options in "WPML > String Translation". 2. Modify the code to handle comma-separated string outputs for multiselect fields:
Edit \wp-content\plugins\wp-user-manager\includes\fields\types\class-wpum-field-multiselect.php<br />Replace the entire get_formatted_output() function with the provided code snippet that includes WPML translation filters.
We have contacted the plugin authors to update their code accordingly. If the solution provided does not resolve your issue or seems outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening 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 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 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: If you're experiencing an authentication error ('Errore di autenticazione, contatta il tuo responsabile delle traduzioni per verificare il tuo abbonamento') while trying to translate a product using WPML, even though your license is valid, it might be due to a plugin conflict. Solution: We recommend deactivating the 'Add Admin CSS' plugin on your site, as it could be causing the conflict. After deactivating, please clear all caches (site, browser, server) to see if the issue resolves. Additionally, you may need to cancel any in-progress translation jobs at WPML -> Translation Dashboard -> Jobs. Test these steps and observe if the authentication error persists.
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 issue continues, please open a new support ticket at WPML support forum for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
