Problem: The client is trying to translate custom headers in the navigation menu using WPML but is unsure how to manually handle this. Solution: If you're experiencing issues with translating custom headers in your navigation menu, we recommend using the WPML String Translation. This tool allows for the translation of Custom Menu Labels and URLs. For detailed guidance, please refer to our documentation on Translating Menus.
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 is using the WpRentals theme and wants to translate the user dashboard, but you can only translate the titles. Solution: First, ensure a full site backup. Then, scan for the theme and supporting plugin strings from WPML>Theme and plugins localization. Check if these strings are available for translation. For detailed instructions, visit this documentation.
If the issue persists, go to WPML>String Translation, ensure you have a site backup, and enable the Look for strings while pages are rendered option in the Auto register strings for translation section at the bottom of the screen. Visit the frontend pages to see if the issue still exists. This option will be disabled automatically in a few hours. For more information, check this documentation.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, we 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.
Problem: The client reported that the 'Update Translation' button was missing from the Dashboard->Updates section. Solution: We clarified that the 'Translations' section and the 'Update Translation' button in the Dashboard->Updates will only be visible if there is an update available for the plugin/theme strings or if they are missing in the frontend. We recommended checking the attached image for reference on how the 'Update' button should normally appear in the 'Theme and Plugins compatibility with WPML' section. For further details on updating theme and plugin translations, visit the following documentation: Updating Theme and Plugin Translations.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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, you can also contact us directly at WPML Support Forum.
Problem: The client accidentally added an extra language to their WPML translation setup, used all the translation credits, and then removed the extra language. Now, the site is not fully translated into English, and the client is out of credits. Solution: We explained that unfortunately, we cannot refund translation credits that have already been used, as detailed in our documentation: Refunds for Automatic Translation Credits. We recommended activating the pay-as-you-go subscription, which offers the lowest cost per word and includes 2000 free credits. Additional usage is billed the following month. Details on this subscription and pricing can be found here:
If this solution does not apply to your situation, 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 changed the default locale from 'en_US' to 'en_GB' in WPML, and the translations for 'Gridbuilder ᵂᴾ' are not appearing on the English pages despite being visible in WPML > String Translation. Solution: We recommend regenerating the MO files to ensure WPML pulls the strings from the correct locale. Please navigate to WPML -> Support -> Troubleshooting and click the 'Show custom MO Files Pre-generation' dialog box button. Then, click the blue button to regenerate custom MO files. If this does not resolve the issue, it may be necessary to manually create and rename copies of the MO files to match the new language locale. For detailed steps, please visit https://wpml.org/errata/string-translations-are-not-displayed-when-a-language-locale-is-changed/.
If the solution provided does not apply or is outdated, or if you encounter further 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. Should you need additional assistance, please do not hesitate to open a new support ticket.
Problem: The client's website is disconnected from WPML, and the supporter's test link is still present in the WPML account. The client needs to reconnect their website and remove the old supporter's test link. Solution: 1. Go to WPML → Translation Management and click on the Tools tab. 2. Expand the Connected sites dropdown. 3. Click the unlink icon next to the site you would like to disconnect. For more detailed instructions, please visit Automatic Translation Subscription for Multiple Sites.
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 contact us through the WPML support forum.
Problem: The client is experiencing a redirect issue where a category page is incorrectly redirecting to a product page. Both the category and the product have the same slug 'sac-en-paille-marocain', which is causing the redirection. Solution: 1. Clear the website's cache, including server-side cache, to ensure no old redirects are stored. 2. Verify that no redirects are set in the Redirection plugin. 3. Change the slug of either the translated product or category to ensure they are unique. This step should resolve the conflict and stop the incorrect redirection.
If these steps do not resolve your issue, or if the information provided here becomes outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
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 for further assistance.
Problem: You are seeing an error message on your dashboard while managing WooCommerce payment gateway settings. The error details include issues with unrecognized characters in the encoded string. Solution: We recommend you try the following steps to resolve the issue: 1. Close the error message by clicking 'x'. 2. Refresh your dashboard to see if the error persists.
If the error continues, it might be due to reasons that are no longer relevant or applicable to your current setup. 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 still persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing style issues and a key table error that prevented pages from being viewable. Solution: We ran the database troubleshooting options, which resolved the issues, and the pages are now viewable again.
If this solution does not relate to your issue, or if it seems outdated, we recommend opening a new support ticket. We also advise 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.
For further assistance, please visit our support forum.
Problem: The client reported that despite correct translations in the WPML string translation section, some sentences on certain pages of the Spanish version of their website were displaying in English. This issue was not present in an older staging version of the site. Solution: We identified that the issue was due to a conflict between language files from WPML and another language file. We recommended the following steps: 1. Ensure to back up your data. 2. Remove the language files or folders located outside of the
wp-content/languages/wpml
directory to avoid conflicts. 3. Do not drag these external language files into the WPML folder as it can overwrite existing translations. 4. If the issue persists, restore the
wp-content/languages/plugins
folder and remove the language files one by one to find the problematic file. 5. Uncheck the option "Cerca le stringhe durante il rendering delle pagine" to avoid rendering issues.
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. 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: If you're setting up WPML and cannot see the names of the languages to choose (Default language - Translation languages), and activating WPML disrupts the Elementor builder and styles, you might be facing a similar issue. Solution: We recommend reactivating WPML along with the WPML setup wizard. The issue with not seeing language names and the disruption of Elementor could be due to a stuck key in the "icl_admin_messages" table in your database. Removing this key should resolve the problem. If the styling issues persist after this fix, it's advisable to address them in a separate support ticket.
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's site is set to Translate Everything Automatically mode, but a newly created product category did not get automatically translated. Solution: We explained that automatic translation is only possible with the Advanced Translation Editor for specific content types such as posts, pages, templates, and other contents covered by our addons. To translate a product category automatically, the client should edit the original product category and then send a product with this category to automatic translation. Alternatively, creating a draft product, assigning all product categories, and sending it to automatic translation will also translate any product category not yet translated. For more details on translating taxonomies, we recommend reading our documentation here: Translating Post Categories and Custom Taxonomies.
If this solution does not apply to your case, or if it 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. If issues persist, we highly recommend opening a new support ticket for personalized assistance.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
