Problem: The client is facing an issue with duplicated WooCommerce attributes in different languages on a WPML-stabilized site. They want to consolidate these attributes without breaking products, filters, SEO, or using destructive SQL. Solution: We recommend checking if the duplicated attributes appear at Products > Attributes in the WooCommerce section. Here, WooCommerce should only display attributes created in the site’s default language, as this is the canonical source. Translations are managed through WPML’s Taxonomy Translation interface, not listed as separate attributes. It's important not to merge translated taxonomy slugs back into one, as this would disrupt language-specific filtering and URLs. Instead, ensure attributes are registered once in the default language and then translated via WPML’s taxonomy translation. This approach maintains functionality for products, filters, and SEO. If duplicate attributes in other languages appear as separate entries in the admin list (e.g., 'Destinos', 'Duración'), these might have been manually added and are not linked to the originals in WPML’s translation tables. In such cases, deleting these manual entries at Products > Attributes is advisable.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is trying to set up WPML to automatically translate all current and future product reviews into English and German. They are specifically looking to configure WPML to recognize and translate new review strings under the domain 'wcml-reviews' automatically. Solution: Currently, only Post Types and Taxonomies can be translated automatically in the background. Strings from WPML > String Translation cannot yet be automatically translated when using "Translate everything automatically". The client will need to create jobs for those strings and send them to be translated automatically. You can even send entire text domains to automatic translation. For more details on translating product reviews, we recommend visiting this guide.
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 further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client is experiencing inconsistencies between the Dutch and English WooCommerce pages, specifically with price and stock information. The Dutch version shows correct stock status and price, whereas the English version shows the product as available only on backorder and the price as 0, despite correct settings in the backend. Solution: We recommend the following steps to address the issue: 1. Increase the WordPress memory limit to at least 256MB by adding
define('WP_MEMORY_LIMIT', '256M');
to the wp-config.php file, just before the line that says /* That's all, stop editing! Happy publishing. */. 2. Synchronize product taxonomies by going to WPML → Support → Troubleshooting in the WordPress dashboard, selecting Products from the dropdown menu in the Cleanup section, and clicking the Synchronize Post Taxonomies button. 3. Update and complete product translations for all products using Elementor by going to WPML → Translation Dashboard, selecting all the WooCommerce products, and sending them for translation through the Advanced Translation Editor. Ensure all translation segments are 100% complete. 4. Adjust the custom field settings by going to WPML->Settings->Custom Fields Translation, clicking on show system fields, searching for the field _plus_meta_product_voorraad_details, and marking it as copy. Then, update the product in the default language and translations. Documentation:Translating Custom Fields
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 the problem persists, please open a new support ticket.
Problem: The client reported that suddenly the prices on their multilingual website (English and Danish) appeared without tax included, despite the tax settings being correctly configured at 25% for Danish and 21% for English. The client had already checked cache, logs, deactivated most plugins except WPML and WooCommerce, and verified all relevant settings without finding any issues. Solution: We reviewed the WooCommerce settings and confirmed that the option 'Yes, I will enter prices inclusive of tax' was enabled under WooCommerce → Settings → Tax → Prices entered with tax. This setting means that the prices entered by the client already include tax, and WooCommerce is designed to calculate and show the tax portion within that price. For example, if a product price of $100 includes 10% tax, WooCommerce will display the price as $100 on the front end, with $9.09 of that amount being the tax. We verified that the products were displaying prices correctly on the front end. We asked the client to confirm if they were seeing different prices on their end or if other products were showing incorrect values, and to provide URLs of the products along with their current and expected prices if discrepancies were found.
Please note that this solution might be outdated or not applicable to your specific 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 needed, please open a new support ticket.
Problem: The client reported a crash on Greek product pages when using the Klarna for WooCommerce plugin, despite it working correctly in other languages. The error logs indicated a fatal error due to a null object reference in the Klarna plugin, suggesting a conflict with WPML's handling of translated products and WooCommerce Blocks.
Solution: We initially attempted to resolve the issue by applying a temporary code snippet to check for null product objects on the Greek product pages. However, this did not fully resolve the issue. The client managed to fix the display of the Greek product pages by correcting the template used, but the Klarna plugin still caused crashes when enabled. We recommended creating a staging site to further investigate the issue without affecting the live site.
If this solution does not apply to your case, or if it 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 at WPML support forum.
Problem: The client was unable to translate the cart and checkout pages to German using modern blocks instead of the legacy PHP version. Solution: We recommend going to WPML > Theme and plugins localization, selecting WooCommerce, and clicking the scan button. Wait for the scan to finish. This should resolve the issue and display the cart contents in German.
Please note that this solution might be outdated or not applicable to your specific case. 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.
