Problem: The client is experiencing 404 errors on the order confirmation page and the endpoint 'order-paid' in translations. The issue temporarily resolves by saving the permalinks but reoccurs the next day. Deactivating the WPML String Translation plugin stops the error. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation and ensure that the endpoints are set to their original English values (not translated). 2. Save the permalinks again to resolve the current 404 errors. 3. Return to WPML → String Translation and translate the endpoints as needed. Important: After translating the endpoints, please do not save the permalinks again. We are aware of this issue and are actively working on a permanent solution.
We already have a development ticket for this problem and are actively working on a permanent solution in future releases.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues 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 here.
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.
