Problem: After updating WPML, the translated homepage redirects to a products page instead of displaying as expected for guests, although it appears correctly when logged in as an admin. Solution: If you're experiencing this issue, we recommend following these steps: 1) Ensure you have a full site backup. 2) Navigate to WPML>>Support page, and click on the Troubleshooting link. 3) On the Troubleshooting page, execute the following actions in the *Clean up* section, waiting 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 4) Go to Settings>>Permalinks and resave the settings.
If the problem persists, it might be due to a plugin conflict. Test with only WPML and essential plugins active, and switch to a default theme if possible. If the issue still occurs, consider providing temporary access to our support team for further investigation.
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 at WPML support forum.
Problem: The client installed WPML for a bilingual website (Croatian and English), but the default language was incorrectly set as English, causing the English content to appear under the Croatian extension (/hr) and vice versa. Additionally, the client attempted to manually switch language codes and flags, which partially resolved the issue, but the English content still appeared under the wrong extension (/hr instead of /en).
Solution: We advised against changing the main language of the site due to potential data loss and complications. Instead, we recommended restoring the site to a state before these changes were made to properly assess and correct the settings. This should be done in a staging environment to avoid further issues. We corrected the flags and language names to ensure they match the correct languages. We also confirmed that the client used the Classic Translation Editor (CTE) and noted that if switching to the Advanced Translation Editor (ATE) is necessary, all content must be retranslated as the editors are not interchangeable.
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 problems persist, please open a new support ticket at WPML support forum.
Problem: You have a second domain installed on a Flywheel account for a French version of your website. Despite clearing the site cache and saving the permalink structure, the second domain is not working and redirects to the main domain. Solution: We recommend contacting the hosting support to address the issue and check if the domain has been set up as an alias or a parked domain as required for WPML to be able to switch language when using the 'a domain per language' method. Customer reached out to the Flywheel support and they managed to correct the DNS settings.
Problem: You are trying to use a product tag as a display rule in GeneratePress, but WPML is not replacing the product tag ID from the default language to the translated language product tag ID during translation. This issue occurs because WPML is copying _generate_element_display_conditions 1:1 without replacing the product tag ID. Solution: To resolve this issue, you need to modify the GeneratePress conditions file to include a WPML filter that correctly translates the product tag ID. Here are the steps: 1. Open the
This modification should ensure that WPML correctly translates the product tag ID in _generate_element_display_conditions.
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.
Problem: The client's homepage is in German, and the English version of the page should be in English. Despite the English translation being completed and marked as 'complete' in the WPML backend, the page still displays in German on the English version of the live website. Solution: We checked the issue and found that all the text was joined together in a single field. We navigated to WPML -> Translation Management and sent the homepage for translation again. After this action, the fields were separated, allowing us to mark all of them as complete and save the translation. This action resolved the issue.
If you're experiencing this issue, we recommend trying the steps we took: navigate to WPML -> Translation Management and resend your homepage for translation. Ensure that all fields are marked as complete before saving the translation.
Please note that this solution might be irrelevant if it's 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 at WPML support forum.
Problem: The client was unable to see the translated focus keyphrases from Yoast SEO in the translation editor without manually searching for them. Solution: We recommended the following steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following XML configuration:
3. Refresh the translation job by making a small edit to the original post or page. After these steps, the focus keyphrases should appear in the translation editor.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing database errors indicating that the 'ID' column in the field list is ambiguous during queries involving WPML translations and Elementor page builder. This issue persists even after reinstallation of Elementor. Solution: We identified that the issue stems from a conflict in the database where the 'icl_translations' table incorrectly includes an unknown column named 'id'. To resolve this, we recommend: 1. Performing a full site backup to ensure data safety. 2. Removing the erroneous 'id' column from the 'wp_icl_translations' table. 3. Running the following SQL query to adjust the 'translation_id' column:
ALTER TABLE wp_icl_translations CHANGE translation_id translation_id BIGINT NOT NULL AUTO_INCREMENT;
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, 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 for further assistance at WPML support forum.
Problem: The client installed WPML on their development website. While the default language displays correctly, the translated version of the website appears broken, with issues in layout, untranslated navigation menus, and other text elements. Solution: First, we addressed the navigation menu issues in both the header and footer. We recommended translating the navigation menus following the detailed instructions provided here: https://wpml.org/documentation/getting-started-guide/translating-menus/. For custom menu links and header buttons, we suggested manual translation methods as shown in this screen recording: https://go.screenpal.com/watch/cZj1bZV91yB. Additionally, to fix styling issues, we inserted custom CSS code into WP > Appearance > Customize > Additional CSS:
If you're experiencing similar issues, we recommend trying these steps. However, if these solutions do not resolve your problem or seem 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 issues persist, we highly recommend opening a new support ticket for further assistance.
Problem: In post type posts, taxonomy tags are all automatically translated, but 99% of them are just copies of the English version. Solution: If you're experiencing this issue, we recommend you navigate to WPML > Taxonomy Translation, select the Tags Taxonomy in the dropdown menu, and manually edit the translations. If you prefer to have them all automatically translated, you can follow the technique outlined here: https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/. Please ensure to delete all the existing taxonomy translations before applying this method.
This solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with WPML creating a potential attack vector for MITM attacks by disabling SSL verification on sandbox installs, this is relevant to you. Solution: We recommend updating to WPML version 4.6.11 or later, as well as updating the String Translation. This update addresses and resolves the SSL verification issue in sandbox environments.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with translating certain strings in the footer and global options of their website using the WPML plugin. Some strings are translated while others are not. Solution: We recommend adding a text domain to the strings that are not being translated. For example, modify your code to include the text domain like this:
<?php echo __("SUBSCRIBE", "mesa"); ?>
After updating the code, please navigate to WPML-> Theme and Plugin Localization and scan the theme or plugin that contains this code for changes to take effect. For detailed guidance, check our documentation.
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.
Problem: The client reported issues with untranslated content and broken functionality on their multilingual website. Specifically, the 'About Us' page had non-functioning sliders, the 'Commissioning' page displayed incorrectly due to CSS issues, and the 'Products' page content was not translated. Solution: 1) For the 'About Us' page, we resolved the slider issue by copying the section name field. We recommend checking the page to ensure it functions correctly. 2) For the 'Commissioning' page, we identified a potential CSS issue. We suggest verifying if custom CSS is applied to this page and adjusting it as necessary. 3) Regarding the untranslated content on the 'Products' page, we need more information on how content is added in the default language to provide a specific solution.
If these solutions do not resolve your issues or if they seem outdated, we highly 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, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You have been using WPML to manage multilingual sites and have encountered an issue where duplicated template files (headers/footers) are not managed independently with the new block editor. When you edit the default language, all translations are overwritten with the default language. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Create a template in the default language. 2. Navigate to WPML-> Translation Management. 3. Send this template to translation. 4. Translate the template using the translation editor. 5. Return to WPML-> Translation Management. 6. Filter by the secondary language. 7. Hover on the translated template name and click edit.
This workflow should help you manage duplicated templates independently. 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. You can do so at WPML support forum.
Problem: The client reported an issue with the WPML Advanced Translation Editor where the progress indicator always shows 100%, even when there are draft segments. Solution: We explained that the appearance of a dash-line status indicates that the sentence is translated automatically. If the sentence is in Draft status, it will display an orange color line instead of a blue color line. Editing the sentence and clicking on Save changes the status to a straight-line, indicating manual translation. In both scenarios, the sentence is considered translated, and the total showing 100% is accurate. For further details, you can visit our forum post: https://wpml.org/forums/topic/advanced-translation-editor-total/#post-16014261
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to translate Elementor Custom Label Values in a select field, but the translated options appear on one line instead of new lines, causing the form to not function properly. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to the top right corner of the translation editor. 2. Click the gear icon. 3. Disable the option 'I prefer bigger segments'. 4. Click Save. 5. Send the page to translate again via WPML > Translation Management. After these adjustments, re-translate the page to see if the issue is resolved.
If this solution does not apply to your case, or if it seems outdated, 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
