Problem: After updating to version 5.5.3, you are encountering a fatal error on the payment page when making a payment in a language different from the original. The error is related to the 'woo-stripe-payment' plugin where it fails to get the currency from an order object, which turns out to be false. Solution: If the issue persists, try disabling and re-enabling your theme, as this approach resolved the issue. Additionally, ensure that your theme and all plugins are updated to their latest versions.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/ and verify the version of the permanent fix. If necessary, do not hesitate to open a new support ticket for personalized assistance.
Problem: You are trying to apply a bulk discount to a variable product's variation prices in WooCommerce, but the change does not apply to the second language on your site. Solution: First, ensure that you update the original product after changing the prices in bulk. In our tests, after bulk updating and saving the original product, the prices appeared synced across translations. Unfortunately, WooCommerce does not provide a global 'Bulk' option for variation prices at Products > All products. You only need to save the original product, and the changes should apply automatically to the translation. If this workflow does not resolve the issue for a specific product, please provide an example of the product where it fails.
Please note that this solution might be outdated or not applicable 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that product galleries were not syncing correctly between different language versions of their website, despite the backend showing the same settings for both. Solution: We recommended the client to first check if the issue persists with newly created products to determine if it's a recurring problem. We also suggested deactivating all other plugins except WPML and WooCommerce to rule out any plugin conflicts. Additionally, making a minor change to the original product, updating it, and then re-translating could help resolve the issue. If these steps do not solve the problem, it might be outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
Problème : Vous tentez de traduire une image pour la bannière d'une archive produit en anglais, mais l'image reste la même qu'en français malgré vos tentatives de modification via l'administration de WPML et l'édition directe de la catégorie. Solution : Les miniatures des catégories sont enregistrées par ID. Pour traduire l'image de la bannière, suivez ces étapes : 1. Allez dans WPML -> Paramètres -> Traduction personnalisée des métadonnées. 2. Définissez « thumbnail_id » sur « Traduire » et enregistrez les modifications. 3. Accédez à votre médiathèque et copiez le numéro d'identification de l'image en anglais. 4. Allez dans WPML > Traduction de la taxonomie > Catégorie de produit et choisissez la catégorie pertinente. 5. Modifiez la traduction et collez l'ID de l'image anglaise, puis enregistrez. Votre image devrait maintenant s'afficher correctement en anglais sur la page spécifiée.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
