Problem: You are trying to translate a button on your homepage into Spanish, but it is not displaying the translation. The button is part of an ACF link called 'Button' from the 'Two Column' ('two-col-all') ACF module, and it is inside the 'CTA' ACF Repeater. Solution: First, ensure that your fields are set correctly in WPML's Custom Field Translation Settings. The Repeater Field should be set to 'Copy once', and the Link field should be set to 'Copy' if you want to use the same link in both languages, or 'Translate' if you need different URLs for each language. You can find more details on setting these options in the documentation. After adjusting these settings, edit the link field on the original content, save the page, and then translate it again. If necessary, use the text search field in the WPML Advanced Translation Editor to find and translate the specific link.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, we highly recommend checking the related 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.
Problème : Si vous avez mis à jour les tarifs dans votre WooCommerce en anglais et que vous constatez que les prix ne sont pas synchronisés dans les autres langues, cela pourrait être dû à la configuration de la traduction des champs spécifiques du plugin tiers utilisé. Solution : Nous vous recommandons de changer la préférence de traduction du champ "gift card amounts" à "COPY" pour permettre la synchronisation des prix dans toutes les langues. .
Si cette solution ne s'applique pas à votre cas ou semble obsolète, ou si vous rencontrez d'autres problèmes, n'hésitez pas à ouvrir un nouveau ticket de support. Nous vous recommandons également de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version des correctifs permanents, et de confirmer que vous avez installé les dernières versions des thèmes et plugins.
Problem: The client is unable to translate certain strings in Gravity Forms using WPML on their website built with Beaver Builder. Specifically, strings like 'First', 'Last', 'Required', 'Enter Email', 'Confirm Email', and others are not being picked up for translation. Solution: We recommended the client to ensure they have a backup of their site, which can be done using the UpdraftPlus plugin. Next, we advised trying to translate the strings directly through WPML's String Translation interface. This can be accessed from the WPML menu in the WordPress admin area. The client should search for the strings under the 'gravityforms' text domain and add translations as needed. It was also noted that some strings, such as 'Choose file' and 'Max file size', are browser-dependent and therefore cannot be translated through WPML as they will appear in the language set by the user's browser.
If this solution does not resolve the 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 further assistance is needed, please open a new support ticket.
Problem: You have translated your site from Danish to English and added links in the main menu. However, when switching languages, two of the links, 'Going on' and 'about', revert to the Danish version despite re-translating the menu. Solution: To ensure that all menu links remain in English when switching languages, you should not attempt to translate templates or menus directly within the site editor. Instead, navigate to WPML > Translation Management > Dashboard. Use the filter on the top left to select the post type you wish to translate. After selecting your content, send it to translation. If you are translating the content yourself, you will need to access the translation at WPML > Translations. For further guidance, refer to our documentation on translating content created using the Gutenberg editor and full site editing at Translating sites that use full site editing.
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.
Problème : Le header ne s'affiche plus en anglais sur la version mobile ANG, mais il s'affiche correctement sur la version mobile FR après la mise à jour de la traduction de la page d'accueil. Solution : Si vous rencontrez ce problème, nous vous recommandons de vérifier si les styles appliqués à l'en-tête traduit nécessitent des ajustements. Vous pouvez trouver des instructions pour gérer les styles des éléments traduits dans notre documentation sur l'utilisation de différents éditeurs de traduction pour différentes pages : https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/#how-to-use-manual-translation
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous conseillons 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.
