Problem: The client is experiencing an issue where the language switcher appears twice in the menu of their website: once as the first item and again as the last item, but broken. They want the language switcher to appear only once as the last item. Solution: We recommend clearing your browser cache as a first step, as this might resolve the issue of seeing the language switcher incorrectly. To do this, you can follow the steps provided in this documentation: WPML Language Switcher Options. If after clearing the cache the issue persists, it might be due to a configuration or a visibility issue that is not replicable on our end. In such a case, we suggest checking your menu settings in the WPML "Languages" section to ensure the switcher is set up correctly to appear only at the desired location in the menu.
If this solution does not apply or is outdated, or if you continue to face issues, 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 contact us directly at WPML support forum.
Problem: The client is experiencing an issue where the translated taxonomy terms are not showing on the front end when the Dynamic Visibility feature by Jet Engine is enabled, although they appear correctly when the feature is disabled.
Solution: We recommend the following steps to ensure that the Dynamic Visibility feature works correctly with translated taxonomy terms in WPML:
1. Navigate to WPML -> Settings -> Custom XML Configuration tab.
2. Add the following code:
3. Save the changes.
4. Go to the page and edit in the default language, make a minor change (like adding a dot or word), and save.
5. Update the translation.
6. In the translation editor, locate the new fields with the name "jdev_value" and translate these as the names of these taxonomies.
7. Complete the translation to 100% and check the frontend.
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 the problem persists, please open a new support ticket.
Problem: You are trying to translate Elementor heading titles and paragraphs on your site but the translations are not displayed, only the original language. Solution: 1) Translate the template ID via WPML-> String Translation. After this step, the strings should work correctly in both languages. 2) To translate the related listings widget, add the following XML code in WPML-> Settings-> XML tab:
Please verify if the translations are now correctly displayed.
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 is unable to translate the first horizontal timeline on their page using WPML because the Elementor Timeline Addons Plugin is not compatible with the WPML editor. Solution: We recommend adding the following custom XML configuration to WPML to make the Elementor widget translatable:
After adding this code, make a small change and re-translate the timeline. Additionally, we suggest sharing this solution with the plugin author and inviting them to join our GoGlobal program to enhance compatibility.
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.
Problem: The client needs to register an additional site, affitti.bosa.net, but their account is currently registered only for bose.net. Solution: If you're experiencing this issue, it's likely because you are using an End-user (one-site) license. This type of license is limited to one site only and does not allow for the registration of additional sites or license changes. For more information, please check out the following link: Transferring Account Renewals to Your Clients. To register more sites, you will need to purchase a new license. You can do this by visiting WPML Purchase Page. If the system does not allow you to purchase from the same account, you may need to create a new WPML account.
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 WPML 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: The client was facing an issue where the 'read more' text in the posts was not translating correctly using WPML, despite other text translations working fine. This issue persisted even after deactivating the Post Type Order plugin and rebuilding the template. Solution: We identified that the untranslated 'read more' text was part of a Toolset template. To resolve this, we translated the specific text using the WPML Advanced Translation Editor (ATE) via the Translation Management section. After applying the translation directly in the Toolset template, the 'read more' button text displayed correctly in the desired language.
Please note that this solution might be outdated or not applicable to your specific case. If you're still experiencing issues, we recommend checking the related 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 was experiencing a critical error when switching to the German language on their website. Additionally, when in the English language, three products were displayed in German, which was not the case previously. Solution: We identified that the issue was due to the string "Alle %" not being translated properly. We corrected this translation issue, and the website should now function correctly without the critical error when switching languages. If you're experiencing similar issues, we recommend checking the translation of all strings in your WPML String Translation module.
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.
Problem: The client is developing a site and is unable to translate the title content in the mega menu using WPML. They asked why WPML is not translating the title content and if specific settings need adjustment. Solution: If you're experiencing issues with translating title content in your mega menu using WPML, we recommend switching to the alternative language in the menu section of WordPress and editing the mega menu content directly from the menu admin page for that language. It's important to avoid making changes within the translation editor for elements managed through it, as this will disrupt synchronization. Any future modifications to the default language will overwrite manual changes made in this way. Additionally, please refrain from altering strings containing page content in the icl_strings table to avoid potential issues.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client was unable to view the Spanish version of a product page despite translating it. In the backend, a plus icon indicated the need for translation, which persisted even after translating. On the frontend, switching to Spanish would reload the page in the default language.
Solution: We identified that caching plugins might have caused the issue. We deactivated the caching plugins and switched to the 2024 theme. After editing the page and adding a Spanish translation, the issue was resolved, and the Spanish page displayed correctly both in the backend (showing a pencil icon) and on the frontend.
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client needed help translating tax labels and terms and conditions on their WooCommerce checkout page into multiple languages using WPML. Solution: We advised the client to use the WPML String Translation module to translate the strings. Here are the steps we recommended: 1) Navigate to WPML>>String Translation. 2) Search for the strings that need translation. 3) Change the language of the strings from Greek to English. 4) Translate the strings into Greek from English. For more detailed guidance, please refer to our documentation on how to change the source language of strings.
Please note that 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: In your blog using the Blocksy theme, you are facing an issue where translation labels for links to the profile and log-out are not updating after switching languages, despite being translated in WPML > String Translation. Solution: We recommend adding the following XML code to WPML > Settings > Custom XML Configuration to register the dropdown fields for translation: https://wpml.org/forums/topic/the-button-label-does-not-change-in-the-blog-when-languages-have-been-switched/#post-15839077
If you are using a child theme, adjust the first key name to
<key name="theme_mods_blocksy-child"></key>
. You can find the correct option name from the table wp_options in the database. After adding the code, go to WPML > String Translation and translate the strings there. Check the translation strings in the frontend. For more details, refer to the documentation on translating strings in the wp_options table.
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.
If this solution does not apply or is 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 for further assistance.
Problem: The client is trying to translate the blog page and the category page using Toolset templates, that fully compatible with WPML. Despite using the advanced translator, media translation, and string translations for elements like the slider texts, some texts, sidebar images, and the slider in the hero section remain untranslated in the default language, Spanish. Additionally, the blog category page automatically switches from Spanish to French, and outdated translated versions of the page persist. Solution: We identified that a plugin conflict was causing the translation issues. There was a plugin, called "Post Types Order" by Nsp code, that was causing the issue. If the problem persists or if you encounter new issues, we advise opening a new support ticket. For further assistance, please visit our support forum at https://wpml.org/forums/. Additionally, it's crucial to check for any related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure that you have installed the latest versions of themes and plugins. If this solution does not apply to your case because it might be outdated or not relevant, please do not hesitate to open a new support ticket.
Problem: When using WooCommerce with the PluginHive 'Multi-Carrier Shipping Method for WooCommerce' plugin and WPML, USPS international shipping methods are not offered for customers with international shipping addresses selecting the Spanish language. This issue arises because the translation of the country name includes accents, such as g 'Canada' to 'Canadá', leading to an invalid country name error (error code -2147218046) from USPS. Solution: The issue primarily stems from the PluginHive plugin rather than WPML, as similar issues would occur in a Spanish WooCommerce setup without WPML. The PluginHive developers are aware and plan to address this in their next release. If immediate resolution is necessary, consider implementing custom code using the
wpml_switch_language
hook to ensure the correct country name is used in API requests.
If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify you have the latest versions of your themes and plugins, and consider opening a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue with the language switcher in DropDown format on their mobile device. When pressing the ∨ button, it automatically jumps to English, preventing the selection of other languages, whereas on PC, hovering over it displays other languages for selection. Solution: We recommend modifying the CSS to prevent the current language from being clickable on mobile devices. This can be achieved by adding the following CSS code:
This change should resolve the issue by disabling the link action when the ∨ button is pressed. If this solution does not resolve the issue or if it becomes outdated, please check our 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 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
