Problem: The client created a custom code block inside the Divi Builder for WooCommerce product templates and translated the text using WPML's String Translation. However, the translations were not visible on the product pages when switching to English. Solution: 1. We recommended that the client create a shortcode to handle the custom code block. This involves adding the following code to the functions.php file of their theme:
2. Replace the custom code module with a text module in Divi and use the shortcode
[product_feature_box]
. 3. Go to WPML's String Translation and search for the texts of the code to find them for translation, or use the Domain select box and select the "your-text-domain" domain item to show all the text for translation in one place.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 the problem persists, please open a new support ticket.
Problem: The client needs a feature where if a user is not from the main country, the website should use English as a fallback language, regardless of the browser language. Solution: We explained that while WPML does not have a built-in feature for this specific redirect behavior, it is possible to achieve this by using WPML's hooks for a custom solution. We provided two hooks that could be useful:
We also suggested exploring general web development techniques for detecting a user's browser language and implementing redirects, referencing a StackOverflow thread for guidance.
We recommended backing up the website before implementing any custom code. If the client is not comfortable with custom coding, we suggested reaching out to one of our certified contractors for professional assistance.
If this solution does not apply or is outdated, or if further assistance is needed, we encourage the client to check the related known issues, verify the version of the permanent fix, ensure the latest versions of themes and plugins are installed, and if necessary, open a new support ticket at WPML support forum.
Problem: The client was unable to fully translate a page using the WPML translation editor. Only parts of the page were loading, and even though the translation was marked as complete, switching the language showed that half of the page was not translated and was displayed in the default language.
Solution: 1. We removed the list block from the page and updated it. 2. We then updated the translation to check if all of the page's strings were visible. 3. We re-added the list block and checked the translation again. 4. We identified that the issue might be related to how a flag was being added to the page. We suggested using an icon instead and then checking if the string worked correctly.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us on the WPML support forum.
Problem: The client is developing a plugin that adds custom emails to WooCommerce and is using WPML to send emails in the current user's language. While the text within the email translates correctly, the WooCommerce email footer, which is an option fetched by a hook, does not translate as expected.
Solution: We recommend following our documentation on sending emails with WPML, which provides guidance on correctly implementing email translations via WPML/WCML. If you're triggering the email from custom code, you should use the WPML hooks provided in the documentation:
Please note that the solution provided 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. WPML Support Forum
Problem: The client is experiencing an issue where changing the user language with a logged-in user does not update the user language in the WordPress user settings. Additionally, there is a problem with translating the WooCommerce email footer text using the
wpml_switch_language_for_email
function. Solution: To ensure the user's Profile language updates based on the language switcher selection, go to "Users > Profile" in the WordPress dashboard and enable the "Set admin language as editing language" option under "WPML Language Settings". This will align the user's language preference with the language chosen via the language switcher.
For the separate issue regarding the WooCommerce email footer text translation, we ask the client to create a new support ticket, as we handle one issue per thread to keep discussions clear and focused.
Please note that the solution provided might be outdated or not applicable to your case. If the solution does 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. If you still need assistance, please open a new support ticket.
