Problem: You are trying to translate the English version of the footer on your website, but the translation is not being applied. Previously, you resolved a similar issue by searching the files in the Divi library and translations, but the problem has reappeared. You have tried editing the document named 'global footer layout' in the theme builder and enabling theme builder translations, but these steps were unsuccessful. Solution: We recommend checking the original language of the footer template. It appears that the footer's original language is Dutch, which might have been the site's default language previously. To resolve this, please follow these steps: 1. Go to WPML > Translation Management. 2. Filter the content by the Dutch language. 3. Find the footer template and translate it into English.
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 visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: If you're writing articles in WordPress and using WPML for translation, and you notice that the double-quote mark (") is displayed as the directional (curly quote mark “”) in the original language Chinese, this might be due to a WordPress issue and not related to WPML. Solution: We recommend deactivating WPML temporarily to verify if the issue persists. If the problem is still there, it confirms that it's a WordPress issue. To display the double-quote mark correctly in the frontend, use the HTML entity. You can find more information on HTML entities here. Additionally, you might find this discussion helpful: Getting Quotation Marks to Display Properly in Posts.
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.
Problem: The client was experiencing an issue where the homepage would reformat when switching to the Spanish version. Solution: We resolved the issue by taking the following steps: 1. We deleted the existing Spanish language homepage. 2. We duplicated the English language homepage. 3. We translated the duplicated page into Spanish.
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: You are trying to remove the footer widget but are unable to do so. You suspect there might be a specific setting in WPML that is preventing the removal. Solution: We found that the issue was due to a plugin conflict. We recommend deactivating all plugins except for WPML to see if this resolves the issue. Additionally, we added a language switcher to your header using a shortcode to display it as a list instead of a dropdown. You can check how to add language switchers using shortcodes in our guide: Adding Language Switchers using PHP and Shortcodes.
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 contact us through the WPML support forum.
Problem: The values in a form are set to numbers, which cannot be translated, and the plugin retrieves the label as the value. In English, the values are 0 or 1, but in the translated form, it shows the label value. Solution: 1. Navigate to WPML -> Strings Translation. 2. Select the domain gravity_from-6. 3. Locate the strings named radio-30-choice-1-No---$0 and radio-30-choice-0-Yes---$800-value. Change the translation of 1 and 0 to match the original strings. This issue has been resolved in the latest version of Gravity Forms Multilingual, version 1.8.0. So, there is no need to apply the above-suggested workaround. If you are still experiencing issues, 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is using a dropdown in the language switcher and wants to display a custom image icon, not a flag, before the current language. Solution: To replace the flag with a custom image icon in the language switcher, you need to create a custom language switcher. We recommend checking our documentation on creating a custom language switcher at Custom Language Switcher. Additionally, you can find useful examples in our support forums:
As a simpler workaround, consider changing the default language flags in WPML by navigating to WPML>>Languages>>Site Languages>>Edit Languages. For more details, refer to Editing WPML's Languages Table and Adding custom language.
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.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
