Problem: The client has cloned their staging site (staging.hposkam.nl) to a live site (hposkam.nl) and WPML has detected a new address, asking whether to mark it as a copy or as a new address. Solution: If you're experiencing a similar issue where your staging site has been cloned to a live site, we recommend marking the original site as a copy. This allows you to manage translations effectively on both sites. For detailed guidance on how to mark your site as a copy using the Advanced Translation Editor, please visit our documentation: Using Advanced Translation Editor when you move or use a copy of your site.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: You've successfully translated your website and WooCommerce webshop using WPML, but the original English version of three products has disappeared from the front end, showing only the Dutch version. Despite the backend displaying correctly, these products are not visible in English on the front end. Solution: First, try the following troubleshooting steps: 1. Navigate to WPML > Support > Troubleshooting. 2. Click on the following buttons: - Synchronize posts taxonomies (Select "Products" from the Dropdown before clicking) - Clear the cache in WPML - Remove ghost entries from the translation tables - Synchronize local job ids with ATE jobs - Assign translation status to duplicated content - Set language information - Fix post-type assignment for translations 3. Clear the caches on your site and browser, then check the frontend again. If the problem persists, it might be due to a misconfiguration in your redirection plugin. Check the following: - Go to "Tools > Redirection > Redirects" in your admin panel. - Remove any redirection rules set for the English language, especially for the affected products. This should restore access to the English versions of the products on the front end.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, 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 at WPML support forum for further assistance.
Problem: The client reported that translations on the checkout page were missing unless the 'Look for strings while pages are rendered' option was checked. This issue was suspected to be related to the WordPress 6.6 update. Solution: We replicated the client's site locally and on a sandbox environment to troubleshoot the issue. It was discovered that the Pro version of the Checkout Field Editor for WooCommerce plugin provides WPML compatibility, which might be necessary for translating the fields properly. We recommend consulting with the plugin's support team to confirm if upgrading to the Pro version will resolve the translation issues.
If this solution does not apply to your case, or if it seems 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where an attribute removed from a product in the default language (English) still remains visible in the translated version of the product (Dutch). The attribute cannot be removed from the Dutch version as it is locked.
Solution: 1. Open the default language product in Edit mode. 2. Make a small change, such as adding a space or a plus sign in the product title. 3. Ensure that the WPML Translation Editor is enabled for all products, as we recommend using the WPML Translations Editor for translating WooCommerce products. 4. Update the product by pressing the “Update” button. 5. Remove the small change made in step 2 and update the product again. 6. Open the translated page in WPML Translation Editor, ensure the translation is 100% complete, press the complete button, and check if the issue is resolved.
If the problem persists, the client should take a backup of their site and navigate to WPML >> Support >> Troubleshooting page, then press the following buttons: - Clear the cache in WPML - [Products] Synchronize posts taxonomies - Remove ghost entries from the translation tables - Synchronize local job ids with ATE jobs - Synchronize translators and translation managers with ATE - Assign translation status to duplicated content - Fix post type assignment for translations - Set language information
If the solution provided does not resolve the issue or seems irrelevant due to being outdated or not applicable to the client's case, we 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. If further assistance is needed, please open a new support ticket: Contact WPML Support.
