Problem: You are working on a DIVI-based site with WPML in two languages (EN and FR). The global header is set through the DIVI theme builder, and the language flags are set through the widget '[wpml_language_selector_widget]'. On the mobile version of the site, the language flags are not clickable, although they work fine on the PC version. Solution: The issue is due to the z-index settings in your DIVI theme. The main row has a z-index of 3, while the columns have a lower z-index, causing the column with the language switcher to be positioned behind the row. To make the language flags clickable on mobile, assign a higher z-index (greater than 3) to the column that contains the language switcher from the Divi editor. Adjusting the CSS as highlighted can also make the language switcher clickable.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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: If you're experiencing issues where the post format and structure break after translating into a right-to-left (RTL) language, it might be due to missing CSS files in the RTL stylesheet. Solution: We recommend checking if your theme's RTL CSS file (style-rtl.css) includes all necessary CSS files. In a case we investigated, adding the following imports to the style-rtl.css resolved the issue:
Please ensure to back up your site before making these changes. Additionally, it would be beneficial to contact the theme author to include these CSS files in the theme's RTL stylesheet to prevent similar issues.
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 at WPML support forum.
Problem: The client reported an issue where the translation status incorrectly showed as pending, even though there were no pending translations. Solution: Initially, we suggested following the instructions in our guide to resolve issues where the translation process is stuck. This guide can be found here: https://wpml.org/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/ When the problem persisted, we identified that 25 translation jobs were stuck in the database with a status of '2' . We resolved this by executing the following SQL command to manually change their status to '9':
update
`icl_translation_status`
set status = 9
where status = 2
If this solution does not apply to your case, 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 https://wpml.org/forums/forum/english-support/.
Problem: You want to automatically translate the English 'Service' page to German, but the Advanced Translation Editor (ATE) and the classic editor display an outdated version of the original content. Even though viewing the original page from within a WPML editor button shows the correct version, the original text to translate is not synchronized in ATE. Solution: We resolved the issue by running the WPML troubleshooting options, canceling the in-progress translation job, and creating a new one. If you're experiencing this issue, we recommend trying these steps. Additionally, if this solution does not apply to your case, or if it seems outdated, please check the 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 the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
If this solution does not apply because it might be outdated or not suitable for 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 open a new support ticket.
Problem: The client is unable to access WPML>>Settings>>Taxonomies Translation due to a fatal error indicating a type mismatch in WPML_WP_Roles::get_highest_level(). Solution: We recommend logging in as a different admin user to verify if the issue persists. Additionally, it's crucial to perform a full site backup before attempting any fixes. You may also want to try the workaround suggested in a related support ticket, which can be found here: related support ticket.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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.
Problem: The client is unable to see the translated product brands in French on their website using the Kadence Theme Shop Kit. The brands are visible in English but not French and the language selector is missing when editing a brand. Solution: We recommend checking if the Product Brands taxonomy is set as Translatable in WPML. You can do this by navigating to WPML>>Settings>>Taxonomies Translation.
If the issue persists, please perform the following troubleshooting steps after ensuring you have a full site backup:
1) Visit WPML>>Support page and click on the Troubleshooting link. 2) On the Troubleshooting page, click on the following options in the *Clean up* section and wait for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables
If these steps do not resolve the issue, the 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 is experiencing issues with translations on their e-commerce site. Specifically, the product brands only show one language button.
Solution: Ensure that the brands are set to be translatable in WPML. Navigate to WPML-> Settings-> Taxonomy Translation and set it to translatable.
If the solution provided here 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: If you're experiencing a PHP Fatal error after updating WPML, it might be due to a conflict with the Codevz Plus Plugin. This plugin blocks the wpml.org domain, which can cause issues with WPML functionality. Solution: We recommend deactivating the Codevz Plus Plugin to resolve this issue. Alternatively, you can modify the plugin's code to stop blocking the wpml.org domain. Here's how you can do it:
// Locate the blocked hosts array in your Codevz Plus Plugin file.<br />// Comment out the 'wpml.org' line as shown below:<br />// 'wpml.org',<br />
Please note that the Codevz Plus Plugin is not officially compatible with WPML. We encourage you to contact the plugin authors and request them to join our Go Global Program for compatibility support.
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. For further assistance, you can always contact us through the WPML support forum.
Problem: The client is experiencing an issue where the language switcher on their website is not functioning, despite having translated pages set up. The symptom observed is that the language switcher does not link to the translated pages correctly. Solution: We discovered that there is a 301 redirect affecting the "/fr" link, which might be set up via a plugin, custom coding, or directly from the hosting/domain management panel. We recommend checking these areas to identify and resolve the redirect issue. If the redirect is configured through the hosting/domain panel, it is advisable to contact the hosting/domain support team to assist in resolving this.
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 with us at WPML support forum.
Problem: While developing a site using the Avada theme and making translations, the client noticed that the color palette and global CSS changed unexpectedly. Solution: We recommended checking for similar issues on our support forums by using a custom search URL: Google Search for WPML and Avada CSS issues. Additionally, we suggested that the client clear any existing caches, whether locally or at the server level, as this might resolve the issue.
If this solution does not apply or is outdated, or if the problem persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to find the option to purchase Prepaid Credits for translating their site after using the free Pay-as-you-go credits. They are also unsure if it's possible to switch to Prepaid Credits after using Pay-as-you-go. Solution: If you're experiencing this issue, we recommend that you first navigate to WPML > Translation Management > Tools and cancel your Pay-as-you-go subscription. After doing this, you can purchase Prepaid Credits from here. Once you have bought them, you can assign these credits to your sites as explained in this documentation: How to Assign Automatic Translation Credits to Your Sites.
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 here.
Problem: If you're experiencing issues where column links on your homepage in French are not pointing to the translated French pages, even though they have been fully translated, follow the steps below. Solution: 1. Navigate to WPML-> Settings-> Custom XML tab. 2. Add the following code:
3. Save the changes. 4. Update the page in the default language. 5. Update the translation using the translation editor. 6. Search for the URL and translate it. For more information on registering page builder widgets for translation, kindly 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 needed, please open a new support ticket for further assistance.
Problem: You are trying to translate a pop-up from the Gift Hunt plugin on your site but cannot find where to do this. Solution: We could not find information confirming whether the Gift Hunt plugin is compatible with WPML. We recommend contacting the Gift Hunt support team to verify this. If they confirm compatibility, ask them for the steps to translate the pop-up. You can reach them at hello@gifthuntplugin.com or on their WordPress support page at https://wordpress.org/support/plugin/gift-hunt/. If you receive helpful information, please share it with us in this ticket to assist others facing the same issue.
If this solution does not apply to your case, or if it becomes 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 you still need help, please open a new support ticket at WPML support forum.
Problem: You want to change the name of the language in the footer menu from Norsk bokmal to Norsk. Solution: We recommend navigating to WPML > Languages > Edit Languages. Here, you can edit the language name and save your changes.
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 you still need assistance, please open 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
