Problème: Le client ne peut pas accéder aux champs ACF pour la traduction dans WPML, malgré que ces champs soient configurés pour être traduisibles. Solution: Nous avons conseillé au client de vérifier et ajuster les paramètres de traduction des champs ACF en utilisant le mode "expert". Pour les champs de type texte ou lien, il faut les régler sur "traduire". Pour les champs répéteurs, il est recommandé de les régler sur "copier" et de mettre leurs sous-champs sur "traduire". Après ces ajustements, il est nécessaire d'éditer la page concernée pour que WPML puisse appliquer les nouveaux paramètres et effectuer la traduction. Pour plus d'informations sur le mode expert, vous pouvez consulter la documentation ici : Utilisation de l'option de traduction experte avec ACF et WPML.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, 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: You have a Divi site with WPML and have translated a Divi layout. You want to change the text 'discover this product' to 'discover' but cannot find the string in WPML. Solution: First, we added a custom XML configuration to ensure WPML recognizes the specific shortcode used in your Divi layout. Here is the XML you should add in WPML > Settings > Custom XML Configuration:
If the custom XML configuration does not take effect, the issue might be with the language files. We recommend deleting the language file 'divi-machine-en_US.mo' from the /wp-content/languages/wpml folder. Please ensure to back up your site before making this change.
If this solution 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 is unable to display SVG images on the translated pages of their website using WPML. Despite applying a known workaround, the SVG images still do not appear on the translated version of the page. Solution: We recommend the following steps to resolve the issue: 1. Add the workaround from the errata to your theme's
functions.php
file. You can find the workaround here: WPML Errata on SVG Support. 2. Update the homepage in the original language by making a minor edit (e.g., adding a space at the end of a paragraph). 3. Update the translation of the homepage by opening it in the Advanced Translation Editor (ATE) and clicking 'Completed', even if no changes are made. If the SVG images display correctly after these steps, begin reactivating other plugins one at a time or in small groups on your development site to identify any conflicts. Once the issue reappears, note which plugin was last activated as it may be causing the conflict.
If this solution does not resolve your issue or seems outdated, or if it does not apply 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 the problem persists, please open a new support ticket.
Problem: You are trying to translate pages using WPML, but encounter broken images because the translation URL is incorrect. Specifically, SVG images are not displaying correctly on the translated pages. Solution: We recommend applying the workaround described in the WPML documentation for SVG support. This involves activating WPML Media to handle SVG image URLs correctly. You can find the detailed steps and more information here: WPML Errata on SVG Support.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML Support Forum.
Problem: The client is using a custom language switcher in a shortcode and needs to output the language code (e.g., FR, EN) instead of the full language name. They could not find the option to do this in the custom code. Solution: We recommend navigating to WPML > Languages > Edit Languages, where you can change the language name from its full form (e.g., 'French') to its code (e.g., 'FR'). You should apply this change for each language accordingly.
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.
