Problem: The client is unable to find a string to translate for a new product add-on field, and the label appears blank in the TH (Thai) language backend. Solution: If you're experiencing an issue with translating a new product add-on field and the label is showing as blank, we recommend you try the following steps: 1. Ensure that you have updated the WooCommerce Multilingual plugin to the latest version, which could be either 5.3.2 or 5.3.3. 2. Open the default product in the Editor. 3. Go to the "Product data" section and click on "Add on". 4. Make a minor change in the title of the Addon and then save the Addon. 5. Update both the product and its translation. If this solution doesn't look relevant or if you continue to face issues, please open a new support ticket with us.
Problem: If you're trying to translate the 'Pay via PayPal' payment description text in WooCommerce PayPal Payments and it's not updating, follow these steps to resolve the issue.
Solution: 1. Navigate to the "Translate texts in admin screens" page and register/translate the title and description strings from the "admin_texts_woocommerce-ppcp-settings" text domain. 2. Open the
Problem: The client cannot access the translated version of their home page; it redirects back to the default language. Solution: We have identified that the client is using SmartCrawl Pro v.3.8.1, which has a known compatibility issue with WPML. The solution is to update the SmartCrawl Pro plugin to the latest version, which is v.3.8.2, as the issue has been resolved by the plugin's author in this update.
If this solution does not seem relevant or if the problem persists, please open a new support ticket with us.
Problem: If you're experiencing issues with the WCFM dashboard not working properly after enabling WPML String Translation, where details on the settings page are missing and unclickable, it might be due to an incorrectly translated admin string. Solution: 1. We recommend contacting the authors of the WCFM plugin to help identify the function or source code where the problematic HTML entity is called. 2.
we were able to resolve the issue by finding the culprit that is causing this error, we had to delete any strings translated containing the said percentage : \"%\"and have provided a video explanation of the cause and solution: Video Explanation.
If this solution doesn't look relevant to your situation, please open a new support ticket in the WPML support forum.
