Problem: You are experiencing an issue where the Admin Language Switcher (flags) has disappeared from the WooCommerce Product Attributes page. This problem occurs despite trying different themes and is specific to the Product Attributes screen, as the switcher works correctly on Posts, Pages, and Product Categories. Solution: We recommend translating the Attributes through the correct section in WPML. You should navigate to WPML > Taxonomy Translation to translate both the Attribute name and the attribute terms. For detailed guidance on translating WooCommerce elements, please refer to our documentation: How to Translate WooCommerce.
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.
Problème : Le taux de change ne fonctionne pas comme prévu, avec un exemple où 1 CHF devrait équivaloir à 1.07 EUR, mais le produit s'affiche à un prix inférieur en EUR. Solution : Le problème semble lié à la configuration des taxes dans WooCommerce plutôt qu'à un problème de code ou de plugin. Voici les étapes pour comprendre et ajuster la configuration : 1. Dans WooCommerce → Réglages → Taxes, assurez-vous que l'option « Les prix sont saisis avec taxes » est activée. 2. Vérifiez les réglages sous WooCommerce → Réglages → Taxes → Taux standards et assurez-vous que les taux de TVA sont correctement configurés pour chaque pays. 3. WooCommerce calcule la TVA en fonction de l'adresse de livraison du client, ce qui peut modifier le prix final affiché selon la localisation du client. 4. Pour tester si d'autres plugins interfèrent, désactivez tous les plugins sauf WooCommerce et vérifiez si le problème persiste. Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions de vos thèmes et plugins, et si nécessaire, d'ouvrir un nouveau ticket de support sur notre forum de support.
Problem: If you're experiencing 404 errors on your translated pages after permanently removing a page and find that re-saving permalinks via /wp-admin/options-permalink.php does not resolve the issue, this summary might help. Solution: 1. Ensure that your homepage is set up correctly. In WordPress, a page set as the homepage should be accessible directly via the main domain (e.g., domain.com) and not through a URL like domain.com/homepage. This setup should apply to both the default language and its translations. 2. If you are using WooCommerce, ensure that you have the WooCommerce Multilingual (WCML) add-on installed and that all related products and categories are translated. This is essential for the correct display of WooCommerce content across different languages. For more details, visit WooCommerce Multilingual documentation. 3. Check that the translated slugs are stored in the wp_posts table, which holds all translated content and slugs, similar to the default language.
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 issues persist, please open a new support ticket.
Problème : Le client a rencontré un problème où certains mots dans une liste déroulante ACF n'étaient pas traduits sur son site multilingue, malgré la traduction de la majorité de la page. Solution : Nous avons recommandé au client de suivre ces étapes pour résoudre le problème : 1. Utiliser l'option de traduction automatique pour les champs ACF spécifiques en suivant les instructions sur ce lien. 2. Activer l'éditeur de traduction pour le produit concerné et le renvoyer pour une traduction automatique, comme expliqué ici : Traduire vos contenus. 3. Appliquer cette méthode à tout autre produit présentant le même problème.
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version des correctifs permanents 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 sur notre forum de support.
Problem: The client needed help translating button texts in a multilingual site using the Shop Kit plugin, which is an additional plugin for Kadence. The texts included 'Winkel', 'In winkelwagen', and 'Kies de uitvoering' in Dutch; 'Shop', 'Im Warenkorb', and 'Wählen Sie die Version' in German; 'Boutique', 'dans le panier', and 'Choisissez la version' in French. The client was unable to find a way to translate these texts directly within the plugin. Solution: We recommended adding the necessary strings from the Admin Texts for translation. This can be done by navigating to the WPML String Translation page from the WordPress admin panel. Once the strings are added, they can be translated using the WPML String Translation tool. We asked the client to check if the translations were applied correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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.
Problème : Vous ne parvenez pas à changer le logo en anglais malgré l'utilisation de la traduction de chaînes et de médias. De plus, vous avez un formulaire de recherche Ivory Search qui affiche le mot "Rechercher" que vous n'arrivez pas à traduire. Solution : Nous avons traduit les identifiants de l'image et des formulaires pour vous. Pour le logo, l'identifiant de l'image traduite est le 16. Veuillez vérifier si le logo en anglais s'affiche correctement maintenant en visitant votre site en anglais. Si l'URL de l'image traduite ne fonctionne pas, vous pouvez essayer de la recharger ou de vérifier son chemin d'accès correct dans la section de traduction de médias de WPML.
Si cette solution ne résout pas votre problème ou semble dépassée, 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 sur notre forum de support.
Problem: The client needed help with translating all ACF group fields described as "Nothing to configure" and resolving URL issues where a previously deleted page's URL slug turns into "__trashed". Additionally, there was a problem with 404 errors after permanently removing a page. Solution: 1) For translating ACF Options Page custom field groups: - Set a translation preference for the field group. - Add values to the custom fields in the default language and update. - Switch to the desired translation language using the language switcher and add translations. Detailed instructions can be found here: Translating the ACF Options Page Custom Fields with WPML. 2) For the URL issue: - If the page is in the Trash, restore it and then translate. - If the page is permanently deleted, empty the Trash, create a new page, and translate it.
If this solution does not apply to your case because it might be outdated or not relevant, 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 WPML Support Forum.
Problem: You are experiencing an issue where WPML is not filtering WooCommerce product categories by language on the frontend. All categories from all languages (Greek, English, Bulgarian) are showing together in category widgets and menus.
Solution: We recommend adding
suppress_filters=0
or
suppress_filters = false
to the arguments in your
get_terms()
function to ensure that taxonomy queries return results only in the currently viewed language. For more details on how to implement this, please refer to our documentation on achieving WPML compatibility for themes and plugins: Filter Correct IDs.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: If you're trying to translate the content of the "Divi Pixel FAQ" module and can't find the strings anywhere, we recommend following these steps. Solution: 1. Navigate to WPML >> Settings > Post Types Translation. 2. Set the FAQ or “dipi_faq” post type to "Translatable - only show translated items". 3. You should now be able to translate the FAQ post type posts as normal posts/pages. For more details, check out our documentation on translating custom posts. If the issue persists, please add the debug report in the Debug Information box. You can find instructions on how to provide this information here: provide debug information for faster support.
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 this does not resolve your issue, please open a new support ticket.
