Problem: The client is experiencing an issue where after translating a page to a second language, any subsequent edits to the original language page cause the translation to revert to the original language content. Solution: If you're experiencing this issue, it's important to ensure that you're translating content independently rather than syncing it from the default language. To do this correctly, follow the steps in our guide:
Make a small update to the default language page and then update the translation.
If these steps do not resolve your issue, the solution might be outdated or not applicable to your case. 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 you still need help, please open a new support ticket.
Problem: The client is trying to optimize an English website for a French-speaking audience using French keywords with the Yoast SEO plugin on English pages.
Solution: We explained that once the WPML SEO plugin is activated, it allows for the translation of various Yoast SEO plugin fields. This means that when translating content, the client also has the option to translate SEO-related information, which will be reflected in the translated post/page.
To include French keywords on English pages, the client can use the Yoast SEO plugin's meta box in the Editor to enter Meta titles, descriptions, keywords, and other SEO-related properties. The client can add French keywords in the meta fields to optimize English pages for a French-speaking audience without changing the content language.
When translating English content into French, the keywords entered in the meta fields will be available for translation in the Editor, allowing the client to translate them as needed.
We also recommended consulting the official documentation and support team of the Yoast SEO plugin for additional details on the Meta box and referred to a guide on optimizing page titles for SEO: https://yoast.com/page-titles-seo/.
If this solution is not relevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. 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 contact us in the WPML support forum.
Problem: The client wants to integrate a function to convert Traditional Chinese to Simplified Chinese using the Autohan plugin, and incorporate this option under the WPML language switcher menu.
Solution: We do not provide support for custom coding. However, we recommend checking the following resources for guidance:
If you require additional custom work, we suggest contacting WPML Contractors.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If so, we highly recommend checking 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 issue persists, please open a new support ticket.
Problem: The client is unable to create redirects for their multilingual sites using WPML. The redirects for the main English URLs work, but when attempting to create redirects for other languages, the pages still load as 404 errors.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing issues with WPML where text breaks randomly, and paragraphs start with the previous paragraph's punctuation. Additionally, there are unwanted tags displaying that cannot be assigned to text in the translation.
Solution: We observed that the original text is highly formatted, which results in content being broken into different HTML tags such as
SPAN
,
A
, and others. This is expected behavior in the Advanced Translation Editor (ATE) when dealing with formatted text. The ATE highlights text with formatting markers to allow the same styling to be applied to translations without editing HTML directly, preventing the risk of breaking the page structure or producing bad HTML. Learn more about HTML markers in ATE
If the issue persists and does not fit the scenario described, we recommend checking other text that may be breaking. If there is no such case, please provide further details.
Regarding the removal of unwanted HTML markers, currently, there is no option to do this directly in the ATE. This has been filed as a feature request. As a temporary solution, you can save the translation with the HTML marker in ATE and then manually edit the translated page to remove the link. Guide to manually editing translations Discussion on removing HTML markers
Please be aware that mixing translation editing between ATE and manual editing in the WordPress editor has some implications and should be approached with caution. For more details, see:
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly 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 you still need assistance, please open a new support ticket.
Problem: The client was unable to display the content of three tabs created for WooCommerce products using the "WooCommerce Tab Manager" plugin in the Arabic translation of their website, even though the names of the tabs were visible after using automatic translation.
Solution: We checked the client's website and found that the Translation preference for the Global Tabs was set to "Not Translatable", which was causing the issue. Here are the steps we took to resolve it: 1. We navigated to WPML > Settings → Custom Field Translation and activated the Show System Fields option. 2. We searched for "Tabs" and located the Global Tabs (global_tab_2345) associated with the product. 3. We changed their Translation preference to Copy. 4. We updated the "Minimalist Art Trophy" product without making any changes. 5. After updating the Arabic translation, the Tab contents began displaying correctly. For more information about updating the translation preference of custom fields, please check this documentation.
If this solution does not apply to your case because it might be outdated or not relevant, 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. If further assistance is needed, please contact us in the WPML support forum.
Problem: The client needed to receive the "new order" admin email in just one language (English), despite the site running in five languages.
Solution: We explained that the notification email sent to the admin is always in the site's default language. If the client wants to receive the notification email in a different language, they should change the language in their user profile by navigating to "Users > Profile". After adjusting the language settings in the profile, they can use the following hook to receive emails in the language set for their profile:
We also clarified that translating fields in the email template will not affect the customer side, as the content will be shown in the translated language to the customers.
If this solution does not apply to your situation, or if it seems outdated, 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 you still need assistance, please open a new support ticket.
Problem: The client inquired whether the WPML plugin will utilize the new 'performant translations' feature introduced in WordPress 6.5, which converts .mo files to .php files to benefit from OPCache. Solution: We informed the client that we are aware of the upcoming updates in WordPress 6.5 and are actively working to ensure maximum compatibility with the new 'performant translations' feature. While we cannot provide a specific timeline for when the updated code will be released on our end, we assured the client that our development team is actively addressing this topic. Any updates related to this feature will be included in the release notes of our future updates.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If this is the case, we highly 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 you still need assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client was trying to set up a multicurrency site with euro and Serbian dinar but encountered an issue where the currency switcher was not displaying correctly on the Serbian version of the site. Instead of the switcher, a shortcode was visible. The client had already ruled out plugin conflicts by deactivating all plugins except WPML and WooCommerce.
Solution: We accessed the client's website and deleted the translation for the "%code%" strings in the WPML String Translation, as these should not be translated because they are variables, often indicated by the % symbol. After this adjustment, the currency switcher appeared correctly on the provided page.
If you're experiencing a similar issue with the currency switcher on your multilingual site, we recommend checking the WPML String Translation for any translated variables (especially those containing the % symbol) and removing those translations. Variables should not be translated as they are placeholders for dynamic content.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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 with us.
Problem: Der Kunde hatte Probleme beim Ausgeben einer Liste von Beiträgen und erhielt stattdessen eine Reihe von Fehlern vom ACFML-Addon. Lösung: Wir empfehlen, alle Plugins kurz zu deaktivieren und dann wieder zu reaktivieren. Dieser Schritt hat das Problem auf der Testseite des Kunden behoben. Wenn der Fehler erneut auftritt, sollten Sie uns dies mitteilen.
Bitte beachten Sie, dass diese Lösung möglicherweise nicht mehr relevant ist, da sie veraltet sein könnte oder nicht auf Ihr Problem zutrifft. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollte das Problem weiterhin bestehen, eröffnen Sie bitte ein neues Support-Ticket.
Problem: The client is concerned that the 'fallback to default language' setting in WPML for untranslated pages and posts might cause Google to penalize their site for duplicate content.
Solution: We reassured the client that using the 'fallback to default language' option does not negatively affect SEO. WPML communicates with Google to ensure that the default content is recognized, and Google will ignore the same content on secondary language pages. Once a post or page is translated, Google will index it as new content, not a duplicate. For more details, the client can refer to our documentation on Displaying Untranslated Content on Pages in Secondary Languages.
If this solution does not apply or is outdated, or if the client is facing a different issue, we recommend opening a new support ticket. It's also advisable to check the related known issues, verify the version of the permanent fix, and confirm that the latest versions of themes and plugins are installed.
Problem: The client is experiencing errors when attempting to add translations to a page or a post after migrating their website to a production domain. The debug log file shows the following error:
PHP Fatal error: Uncaught Error: Call to undefined function mb_ereg_replace_callback() in ....../wp-content/plugins/sitepress-multilingual-cms/classes/xliff/class-wpml-tm-validate-html.php:124
Solution: We have identified that the 'Multibyte String' PHP extension is not enabled on the client's server, which is necessary for WPML to function correctly. We recommend contacting the hosting provider to enable this extension. For more details on the 'Multibyte String' PHP extension, please visit WPML's minimum requirements and the PHP manual.
If this solution does not apply to your case, or if it 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 you still need assistance, please open a new support ticket in our forum.
Problem: The client is trying to translate a heading ('Recently added') in the search modal popup and the Upsells heading ('Customers also bought') on the single product page. These strings are not appearing in the WPML String Translation interface. Solution: 1. We recommend scanning the theme for new strings at WPML > Theme and Plugin Localization. 2. For the 'Recently added' string, it needs to be edited directly inside the Customizer and saved. 3. Then, navigate to WPML > String Translation > Translate texts in admin screens (link at the bottom of the page) to register the string for translation. For detailed steps on finding and translating strings that do not appear on the String Translation page, please refer to our documentation: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 with us.
Problem: The client was unable to access the success page after finishing an order on their WooCommerce site, and instead encountered a 404 error page. Solution: 1. We recommended that the client temporarily deactivate all plugins except for WPML, WooCommerce Multilingual & Multicurrency, and WooCommerce to test if the issue persists. 2. We also suggested switching to a default theme, such as Storefront, to rule out any theme-related issues. 3. We asked the client to provide screenshots of the issue for further clarification. 4. We emphasized the importance of backing up the database before making any changes to the site.
If you're experiencing a similar issue, we recommend you follow these troubleshooting steps. However, please note that the solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, we highly 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. Should the problem persist, please do not hesitate to open a new support ticket with us.
Problem: The client was unable to translate the 'Sort By:' text in Arabic on their WooCommerce shop page, which is generated by the 'Filter Everything PRO' plugin.
Solution: We discovered that the 'Filter Everything PRO' plugin is not currently on our compatibility list. We attempted to use the WPML Multilingual Tools plugin to register the Elementor widget for translation, but it did not expose any strings for translation. We recommend that the client contacts the plugin author to request a compatibility update with WPML. We provided information that could be useful for developers to make their themes/plugins compatible with WPML:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly 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 you still need assistance, please open a new support ticket. 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
