WCML

Problem:
You are trying to cache translated posts but are unable to do so because of the _lsvary cookie, which affects caching behavior on your site.
Solution:
Currently, there is no update from the plugin authors regarding a solution to avoid the _lsvary cookie when caching translated posts. We previously reached out to the authors, and they are aware of the issue but have not provided a definitive solution yet.

We recommend contacting the plugin authors directly for the most recent updates on this issue.

The code below, provided by the client, eliminates the need to vary the cache based on currency. However, this approach is only suitable when a single currency is used per (sub)domain or URL. Please note that this code is untested and provided as-is, as it was not created by our team. We strongly recommend testing it thoroughly in a staging environment before implementation.

add_filter('litespeed_vary', 'unset_litespeed_wcml_vary_cookie', 99);
function unset_litespeed_wcml_vary_cookie($vary_list){
if (isset($vary_list['wcml_currency'])){
unset($vary_list['wcml_currency']);
}

return $vary_list;
}

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. If you still need assistance, please open a new support ticket at our support forum.

Problem:
You want to translate bank account details in WooCommerce to Croatian using WPML, but you only have one bank account and need to disable the second one.
Solution:
Since WooCommerce Multilingual translates content on a 1:1 basis, here are a few approaches you can consider:
1) Implement custom code to handle different bank accounts based on the language.
2) Translate all content, using placeholders (e.g., empty spaces) for fields that should remain empty.
3) Use CSS to hide specific sections for a particular language. Note that WooCommerce might use the same class names for both sets of bank details, which may require additional customization to target them properly.
Alternatively, you can use a regular space or an ASCII whitespace character to make the second bank account details "invisible". You can find various ASCII whitespace symbols here.

If these solutions do not apply to your case, or if they seem outdated, we 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.

Problem:
Wenn die Plugins 'WPML String Translation' oder 'Woocommerce Multilingual & Multicurrency' aktiviert sind, tritt ein kritischer Fehler auf, der das Durchführen von Bestellungen verhindert.
Lösung:
Der Fehler stammt direkt aus dem WooCommerce-Code. Überprüfen Sie die Übersetzung in WPML → String Translation und stellen Sie sicher, dass die Platzhaltervariable %s korrekt beibehalten wurde und nicht zu % oder einem anderen Wert geändert wurde. Hier ist der betroffene Code:

$tax_text = wp_kses_post( sprintf( __( '(includes %s)', 'woocommerce' ), implode( ', ', $tax_string_array ) ) );

Diese Lösung könnte veraltet sein oder auf Ihren Fall nicht zutreffen. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollte das Problem weiterhin bestehen, eröffnen Sie bitte ein neues Support-Ticket.

Problem:
You want to change the default English translation of strings in WooCommerce order confirmation emails but cannot find where to make these changes.

Solution:
We recommend modifying the text directly in your WooCommerce code file to update the content in your default language. After updating, scan the plugins again from WPML->Themes and plugin localization. After that, you can translate the strings from WPML->String Translation.

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 do not hesitate to open a new support ticket at WPML support forum.

Problem:
You are experiencing a 404 error on translated product pages after translating your website into multiple languages using WPML. Additionally, some necessary WooCommerce pages have not been created.
Solution:
First, ensure that the URLs for your translated pages do not contain special characters. For example, instead of using 'é', use 'e'. Here is a corrected URL that should work: https://sinotrukparts.com/fr/categorie-produit/pieces-detachees-howo/pieces-de-essieu-howo/
Second, verify that all necessary WooCommerce pages are created and properly configured in each language. If you're still facing issues, we 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 solution provided here does not resolve your issue or seems irrelevant, please do not hesitate to open a new support ticket. We highly recommend visiting our support forum for further assistance: WPML Support Forum.