Problem: The client noticed that the category name on their product page was in Arabic, and the link was pointing to an Arabic version, suggesting a potential issue with WPML. Solution: We first noted that the client's website was experiencing a database connection issue. After resolving that, we recommended changing the Taxonomies Translation settings by navigating to Taxonomies Translation settings. Following this adjustment, we advised the client to clear their browser cache to ensure the changes take effect.
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 problems persist, please open a new support ticket.
Problem: The client was unable to translate a widget on their multilingual site. Despite adding the widget multiple times and translating it via WPML's String Translation, the widget content was only displaying in Greek, regardless of the language selected. Solution: We took several steps to resolve the issue: 1. We ensured that the 'text_admin' string was registered in WPML's String Translation. 2. We resaved the German translation by adding a space and then removing it. 3. We resaved the page translation, even though the content was not directly from the page itself. 4. Finally, we purged the cache to ensure that the changes took effect.
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. Additionally, 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: If you're experiencing an issue where the footer on the contact page is not translated, despite being translated on other pages of your website, it might be due to a caching issue. Solution: We recommend clearing your cache thoroughly after updating the widget for the specific language. Additionally, ensure that you have saved the 'admin texts' in the 'String Translation' and then saved the page again. To automate the registration of these texts, you can add the following code in 'WPML > Settings > Custom XML Configuration':
This solution might be 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 this does not resolve your issue, please open a new support ticket.
Problem: If you're noticing that some translated pages are appearing on Google even though they haven't been published, and these pages display incorrect logos and theme colors, this might be due to a settings conflict or a compatibility issue. For instance, if your site's translated product page shows a different logo or theme colors compared to the original English page. Solution: First, ensure that you have not inadvertently published the product translations. Check your Translation Preference settings for the Product Post Type and Product Categories Taxonomy. You should have the 'Translatable - use translation if available or fallback to default language' option selected. This setting allows the default language products to be listed in the secondary language on the frontend without translation or content duplication. Next, verify that your Elementor templates for the Header, Footer, and Single Product are translated into the secondary language. You can do this by accessing the following links in your admin area:
If after these checks the issue persists, it might be 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 you need further assistance, please do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: The client is facing issues with reactivating WPML on their website after a rebuild. The main problems include a database error stating 'We have detected a problem with some tables in the database,' no languages appearing in WPML -> Languages, and inability to add languages manually. Solution: We recommend resetting WPML and then reinstalling it. Here are the steps to follow: 1. Go to WPML -> Support -> Troubleshooting. 2. Scroll down to find the 'WPML Reset' option and use it to reset WPML. 3. Reinstall WPML with a fresh download. These steps were tested on a staging site and resolved the issues. If you're experiencing this, we recommend trying these steps on your live site.
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 persists, please open a new support ticket with us for further assistance.
Problem: You are experiencing an issue where the links within your custom dropdown menu (megamenu) created using a UX Block and translated with WPML still direct to the original language pages instead of the translated pages. Solution: First, ensure that the 'terms' shortcode parameter used in your menu is translated. Follow the detailed instructions on how to translate custom shortcodes with WPML here: https://wpml.org/documentation/support/language-configuration-files/translate-custom-shortcodes-with-wpml/. Next, add the following custom PHP code to your theme's functions.php file to make the 'terms' ID translatable:
This will allow you to translate the text and ID for your menu in the translated languages.
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 the problem persists, please open a new support ticket.
Problem: The client reported an issue where taxonomy terms such as 'Year' were not translating correctly on their vehicle listing page, despite having translations available. The default site language had been switched from English to Dutch, which seemed to affect the translation functionality. Solution: We identified that the issue was related to how the theme handled translations within specific PHP templates. To resolve this, we provided a code snippet to modify the theme's PHP file to ensure proper translation registration and application using WPML's hooks:
<?php<br />// WPML Workaround for compsupp-7432<br />if (class_exists('Sitepress')) {<br /> $textdomain = 'motors';<br /> $string_name = 'Motors - WPML String: '.substr($single_name, 0, 20);<br /><br /> if (apply_filters('wpml_default_language', NULL) == apply_filters('wpml_current_language', NULL)) {<br /> do_action('wpml_register_single_string', $textdomain, $string_name, $single_name);<br /> }<br /> // Apply the translation to the string<br /> $single_name = apply_filters('wpml_translate_single_string', $single_name, $textdomain, $string_name);<br />}<br /></code><br /><td class="t-label"> <?php echo esc_html($single_name); ?></td><br />After applying this change, the client was instructed to visit the page in the original language to register the string and then translate it via WPML > String Translator under the 'motors' textdomain.<br /><br />If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Additionally, please check related known issues at <a href="https://wpml.org/known-issues/">https://wpml.org/known-issues/</a>, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum at <a href="https://wpml.org/forums/forum/english-support/">https://wpml.org/forums/forum/english-support/</a>.</td>
Problem: You are using the pay-as-you-go auto-translation feature with WPML and have encountered an issue where it indicates that you don't have enough credits for translation. You are unsure why this message appears and how to manage your credits. Solution: The message about insufficient credits appears because you have reached the safety limit of €100 in a month for the Pay-As-You-Go for Automatic Translation. To resolve this, you need to pay the first €100 to resume automatic translation. You can find more details in the Safety limit charges section of our terms and conditions. To resume automatic translation, click the pause icon on your site, which will prompt you to pay the amount and continue with the translations. Ensure you perform a full site backup before proceeding.
If this solution does not apply to your situation, or if it 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.
Problem: The client has translated a formidable form using WPML, but some translations are not displaying correctly. Specifically, certain fields remain in the original language despite being translated. Solution: We recommend checking the WPML -> Strings Translation section to ensure all necessary strings are translated. For fields not showing as translated, such as '147_field-2941-description', it's crucial to verify their translation status in WPML and update them if they are incomplete. Additionally, if encountering issues with specific strings like '[2850]', which refers to another field ID, it may help to remove and re-add the entry or adjust the string directly in the formidable form settings or WPML string editor. If duplicate strings are found in the string editor, deleting the outdated versions can resolve display issues.
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, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where the Arabic URL of the product category page on their WooCommerce site briefly appears and then redirects to the homepage. Solution: Turning off both "Remove base" and "Remove category base" fixed the issue.
If this solution does not fully address your issue, or if it seems outdated or irrelevant to your case, 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 at WPML Support Forum.
Problem: The client is experiencing issues where the WPML translation editor does not display the target language texts of block contents in post_content, despite the normal WordPress editor showing the target language texts. The client is using WP Import Export Lite and Really Simple CSV Importer for data migration.
Solution: 1. This is a recognized issue with the WPML plugin. We are aware of the problem where translated content does not show in the translation editor after import. Our developers are currently working on a solution. For updates, please check the errata page: WPML All Import - Imported posts don't show the translated content in the translation editor. 2. The code "{"translatedWithWPMLTM":"1"}" found in the blocks of the target language contents is a leftover from the previous website and is not causing the issue. 3. Switching to WP All Import PRO will not resolve this issue as the necessary feature is still under development.
If this solution does not apply to your case, or if it seems outdated, we highly 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 at WPML support forum.
Problem: The client was trying to translate their website using WPML and Elementor. Initially, they managed to translate 100% of the page, but after updating the translation using WPML's translation editor, only 5% of the translation remained visible. Solution: We recommend not using different editors to translate the same page as it can lead to issues like this. To resolve the problem, you should register your Elementor widgets for translation. Please refer to these guides for detailed instructions:
If you prefer manual translation using Elementor, check this guide: Using Different Translation Editors for Different Pages. To recover lost translations, you can look into the page's revisions by following these steps: 1- Go to Pages -> All Pages 2- Switch the language from the top admin bar 3- Edit the translated page using the WordPress editor 4- Check the revisions
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 reported an issue where switching the menu to the Spanish version caused it to fail to load, displaying a continuously spinning icon. Solution: We discovered that the WPeMatico Plugin was interfering with WPML's functionality. We recommend deactivating all non-WPML plugins and switching to a standard WordPress theme to check if the issue persists. It's crucial to back up your database and website before making these changes. If the problem continues, please ensure you have upgraded the shared user to Network admin to allow 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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the qtranslate importer plugin on a site with three languages: Traditional Chinese (default), Simplified Chinese, and English. The Traditional Chinese language is not being recognized correctly, resulting in only two languages appearing in the WPML settings, and the menu not being converted. Solution: 1) Check the language codes used by QTranslate and WPML. Before activating WPML and starting the import process, verify the language codes in QTranslate and then in WPML. If they differ, add a custom language in WPML with the same language code used by QTranslate. For instance, WPML uses the standard codes 'zh-hans' for Simplified Chinese and 'zh-hant' for Traditional Chinese. 2) If the menu is not converting, it might be necessary to manually create the menu in the default language and then translate it.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 WPML Support Forum.
Problem: You are encountering an authentication issue when trying to interact with our API, even after re-registering your access key and increasing the memory limit to 256M. Solution: We recommend going to WPML > Settings > Translation Editor and re-enabling the Advanced Translation Editor (ATE) by saving the changes. This should allow you to translate the content on your site using ATE.
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 our 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
