Problem: The client needs to translate the WBW product filter on their site using WPML but cannot find the strings in the plugin. Solution: We currently do not have the WBW product filter plugin certified for WPML, which means we cannot provide specific guidance on how to translate it. The plugin authors claim compatibility, but there is no clear workflow provided. We recommend contacting the plugin authors to inquire about their compatibility status with WPML. If the plugin supports specific functions with WPML, suggest to the authors that they sign up for official WPML certification through our Go Global Program.
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: If you're experiencing issues with WPML causing random variations in product descriptions on order emails and encountering an 'Unable to register: Site key not matching' error when trying to update, follow these steps. Solution: 1. Ensure you create a full backup of your website. 2. Visit your wpml.org account and remove the existing key for your domain. Generate a new key for your domain. 3. Go to your WordPress Dashboard > WPML > Registration and unregister WPML. Then, re-register using the new key. 4. If the issue persists, it might be due to outdated plugin versions. In this case: a. Deactivate and delete the 'WPML Multilingual CMS' and 'String Translation' plugins. b. Download the latest versions of these plugins from WPML Downloads. c. Navigate to your site's backend > Plugins > Add New > Upload, and upload the 'WPML Multilingual CMS' plugin first and activate it. Repeat the process for the 'WPML String Translation' plugin. Rest assured, following these steps will not result in the loss of your translations or settings. If this solution doesn't seem relevant to your issue, please open a new support ticket with us.
