WCML

Problem:
The client needs a comprehensive guide on translating taxonomies and WooCommerce pages using WPML, especially when automatic translation does not meet their specific needs. They encountered issues where taxonomies were not automatically translated when translating products, leading to incorrect category assignments.

Solution:
1. Taxonomies will be translated automatically along with the posts or products they are assigned to. If you're experiencing different results, we recommend checking your site's settings and providing us with WPML debugging information. More information here: https://wpml.org/de/faq/provide-debug-information-faster-support/

2. For WooCommerce pages, replace any WooCommerce Blocks on the Cart or Checkout page with WooCommerce Shortcodes, as we currently cannot translate new blocks. You can find more about WooCommerce Page Shortcodes here: https://woocommerce.com/document/woocommerce-shortcodes/page-shortcodes/ Strings from these pages can then be translated using WPML > String Translation.

3. Attributes are translated automatically with the product they are assigned to. To translate all global attributes in one job, create a product, assign all available attributes to it, and send the product for automatic translation.

4. If a taxonomy is already translated, it will be synced when translating the post. You can also sync taxonomies at WPML > Taxonomy Translation if WPML recognizes that taxonomies are missing on translated posts.

If the solution provided here does not resolve your issue or 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. If further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client has a multilingual WooCommerce site and needs to use different SKUs for products translated into Latvian, without losing the language switcher functionality. The client also inquired about managing SKUs in different languages using WPML.
Solution:
We explained that in WPML, product translations must share the same SKU to sync stock and prices effectively across different languages. To use different SKUs, the client would need to create separate, original products for each language, which would not be linked as translations and thus would not support the default language switcher functionality. However, the client can create a custom language switcher or button that links to the respective products in different languages. We also provided links to documentation for further customization using hooks:

• WCML Hooks Reference
• WPML Hooks Reference

If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 WPML Support Forum.

Problem:
Der Kunde hat ein Problem mit der Lifting Charge-Funktion in WPML unter WooCommerce Multilingual & Multicurrency. Ein Aufschlag von 5 % wird nur im Checkout angewendet, nicht auf der Produktseite. Der Kunde sieht zunächst den gerundeten Preis, aber im Checkout wird der Preis um 5 % erhöht, was auch auf der Rechnung erscheint, jedoch ohne Rundung.
Solution:
Wir haben empfohlen, die Rundungsregeln in den Currency Settings für jede Währung individuell anzupassen. Eine detaillierte Anleitung dazu finden Sie unter: Währungsoptionen und Rundungsregeln festlegen.

Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.

Problem:
The client reported an issue where the admin received an order confirmation email in the HR (Croatian) language, but the customer received the same email in SI (Slovenian), despite all strings being translated correctly in WPML.
Solution:
We first recommended testing with only the default WordPress theme and essential plugins (WooCommerce and WPML) to ensure that the issue wasn't caused by any other plugin or theme conflicts. Upon testing, it was confirmed that the HR email was sent correctly to the customer under these conditions.
Further investigation revealed that the issue was due to the use of a custom string added in the email content in SL (Slovenian), which was not translated. We advised the client to either translate these custom strings via WPML > Translation Management or to delete the custom strings and revert to using the default provided strings.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.

Problem:
The client is experiencing issues with automatic translations not covering the entire website and products in some languages not being able to be added to the cart. Specifically, the client mentioned that on the staging site, the 'add to cart' button was unresponsive, and on the production site, the quantity appeared as 0 instead of replicating the main language quantity.
Solution:
We reviewed the client's staging site and confirmed that the issue with adding products to the cart was not present in all languages, but only when the stock quantity for certain product variations was set to "0".

We advised the client to check the original product in the WordPress Editor and ensure that the stock quantities are correctly set for all variations. If the stock is not empty, the product should be addable to the cart in all configured languages.

In case the stock is not synced then it might be that systems fields have been altered at WPML > Settings > Custom Field Translation. We recommended ensuring that the WPML configuration changes made to 'copy' settings are correctly applied across all environments for fields like "_stock" to maintain consistent behavior.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please do not hesitate to open a new support ticket with us for further assistance.