Problem: The client is trying to translate product attribute labels in WPML and encounters issues in both String translation and Taxonomy translation. The taxonomy general name is not plural and includes an untranslated English 'Product' prefix, which cannot be corrected through the UI. Solution: To remove the 'Product' prefix from the taxonomy general name and manually add the plural form of the taxonomy singular name, we recommend using a custom filter hook in WooCommerce. Here is the code you can use:
add_filter( 'woocommerce_product_attribute_taxonomy_name', 'custom_woocommerce_attribute_label_plural', 10, 2 );
function custom_woocommerce_attribute_label_plural( $taxonomy_name, $taxonomy ) {
if ( 'pa_your_attribute' === $taxonomy ) { // Replace 'pa_your_attribute' with the actual attribute taxonomy name
// Return the custom label you want
return 'Label'; // Replace with your desired label
}
return $taxonomy_name;
}
This code will change the appearance of the label on the frontend but not in the wp-admin. Alternatively, you could register the original taxonomy in English and translate it into German.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
Problem: You are trying to translate labels, slugs, and attribute taxonomy options using WPML, but the translation interface does not consistently show the WPML default language (German) as the source. Instead, the globe symbol appears under the English flag, making it untranslatable. You have to manually change the language to German, and the label text is shown in English, not the source language. Solution: The default language in WordPress is typically English, depending on the language in which WordPress was installed. To resolve this issue, you need to adjust the source language for the taxonomy labels and strings. This adjustment will enable you to create your translations effectively. It is crucial to ensure that especially the slug is translated, regardless of the source language displayed.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is working on a site under development and is unsure which REST API is required by the documentation. The WooCommerce Legacy REST API is incompatible with High-Performance Order Storage used in WooCommerce 9.x, and the client cannot use legacy WordPress posts storage. Solution: We confirmed that WooCommerce Multilingual is fully compatible with the WordPress REST API (wp-json), which is sufficient for managing translated WooCommerce content. The client does not need any other API, and it always refers to the WordPress REST API. For detailed instructions on setup and configuration, please refer to the following guide: Using WordPress REST API with WooCommerce Multilingual.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 further assistance is needed, please open a new support ticket at WPML support forum.
