Problem: The client needed to translate the "Phone" and "Email Address" fields in the Shipping Address area of the WooCommerce Checkout page, which were added using custom code.
Solution: We recommended the client to try the following methods: 1. Enable the "Look for strings while pages are rendered" option in WPML > String Translation, visit the checkout page to render the strings, and then search for them in the String Translation interface. 2. If the strings are not found, they might be registered as admin texts. The client should follow the process outlined in our documentation to find and translate admin text strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/ 3. As an alternative, use CSS to target specific languages. We provided a custom search URL to find existing tickets with code examples for this method.
If these solutions do not resolve the issue or if they seem outdated or irrelevant, we encourage the client 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 the latest versions of themes and plugins are installed. For further assistance, please contact our support forum.
Problem: The client experienced an issue where WPML reversed the source language of some strings from English to Arabic, causing a mix-up of languages on their English and Arabic pages. Solution: We recommended checking the boxes next to the affected strings, scrolling down to find the option to change the language of those strings, setting it back to English, and then translating them into Arabic again. This solution is based on the guidance provided in the following WPML documentation: How to change the source language of strings.
If you're experiencing a similar issue, we recommend you try the steps mentioned above. However, please note that the solution might be irrelevant due to it being outdated or not applicable to your case. If the issue persists, 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. Should you need further assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client has an online store serving the GCC countries and is using WPML and WCML plugins to translate the store and provide products in local currencies. The issue is that WooCommerce only shows currency symbols in Arabic format, which is not professional, and the client wants to display custom currency symbols for both English and Arabic versions of the store.
Solution: We recommended registering the currency symbol string to a text domain using the following code and replacing "your-domain-name-here" with a descriptive domain name:
If this solution 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. If needed, please open a new support ticket in our support forum.
Problem: The client is using the Blocksy Theme with WooCommerce and is unable to translate additional product tabs created by a pro feature of the theme. These custom tabs do not appear in the Arabic version of the product page, while standard WooCommerce product tabs do.
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 necessary, please open a new support ticket with us.
