Problem:
Updating English translation on ACF option page results in the following fatal error .../httpdocs/wp-content/plugins/acfml/classes/Options/EditorHooks.php rivillä 328
Solution:
Make sure to enable WPML string Translations plugin to solve the issue.
If you're experiencing issues with email translations not working correctly in Gravity Forms, specifically where emails to certain recipients are always in Dutch, this might be due to a recent update (Gravity Forms version 2.10.0).
Solution:
We have identified that this issue related to the new 'Background Notifications' feature introduced in Gravity Forms version 2.10.0. This feature, which is enabled by default on new installations, allows notifications to be sent via a separate request to improve form submission performance.
The problem has been fixed with Gravity Forms Multilingual version 1.8.5.
Problem: If you're experiencing a critical error or a 500 error when launching the Divi builder after activating the WPML Multilingual CMS plugin, this summary might help. Solution: We recommend checking if the issue occurs consistently on all pages or only specific ones. In this case, we were able to open the Divi builder without any issues and did not find any errors in the logs. It might be helpful to verify if the problem persists on different pages or under specific conditions.
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 the problem continues, please do not hesitate to open a new support ticket. You can reach our support forum here: WPML Support Forum.
Problème : Vous rencontrez un problème où WPML traduit les valeurs @type dans le schéma JSON-LD FAQPage généré par Rank Math Pro, ce qui entraîne des erreurs de validation des données structurées de Google. Les valeurs @type comme "Question" sont traduites en "Pregunta", ce qui n'est pas accepté par Schema.org.
Solution : Pour résoudre ce problème, vous devez ajouter un code XML spécifique dans WPML > Paramètres > Configuration XML personnalisée. Voici le code à utiliser :
Après avoir ajouté ce code, modifiez légèrement la page concernée pour que WPML applique le nouveau fichier XML, puis réenregistrez la traduction.
Si cette solution ne résout pas votre problème ou si elle semble obsolète, nous vous recommandons de consulter 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.
Problem: If you're experiencing issues with incorrect escape values when saving option pages using the ACFML (WPML-ACF) plugin, particularly when fields are set to copy or copy-once, the script workflow may not account for the necessary unescaping before saving in other languages. Solution: We recommend updating to ACFML version 2.2.4, which includes a permanent fix for this issue. This update ensures that the
wp_unslash()
function is applied to the local value before saving, correcting the escape values across different languages.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues saving a page in the main language (English) on your Divi5 staging site while WPML is activated, and find that deactivating WPML allows you to save the page, this might be due to a specific error that needs further investigation. Solution: We recommend enabling WordPress debugging to identify any WPML-related errors that could be causing this issue. Here are the steps you should follow: 1. Edit your wp-config.php file to enable debugging. Insert these lines before the comment /* That's all, stop editing! Happy publishing. */:
2. Replicate the error by trying to save the page again. 3. Check the debug.log file located in your /wp-content directory for any WPML-related errors. 4. Copy and paste the full error message here for further assistance.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where not all strings are appearing in the Strings Translation, and specific elements like the hamburger menu in the main navigation remain untranslated, this might be due to the header template not being translated. Solution: First, ensure that the header template is translated. You can do this by accessing the header template in your admin panel and translating it. Here is a general guide on how to translate templates: Translating Your Contents.
If the issue persists, we have implemented a custom code workaround. Add the following code to your functions.php file:
After adding the code, open the translated header template in Elementor and set the correct off-canvas (sidebar) template. This adjustment is necessary for each translated template.
Please note that this solution might become irrelevant due to updates or may not apply 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.
Problème : Le client utilise WPML pour traduire des cours sur un site de e-learning. Après avoir créé un module de formation en français et l'avoir traduit en anglais et en allemand, le client ne peut pas changer la vidéo associée à chaque cours dans les différentes langues. Le support de TutorLMS a indiqué que pour insérer des vidéos dans la langue souhaitée, il faudrait créer trois formations différentes. Solution : Nous avons identifié que dans le fichier XML de Tutor LMS, le champ pour la vidéo était marqué comme « copy ». Pour permettre la traduction de la vidéo, il faut changer ce paramètre en « translate ». Voici les étapes à suivre : 1. Modifier le fichier XML pour que WPML détecte l'URL de la vidéo comme traduisible. 2. Modifier le cours d'origine. 3. Envoyer le cours pour une traduction manuelle. 4. Ouvrir l'éditeur de traduction de WPML. 5. Rechercher l'URL de la vidéo et la traduire deux fois : une fois lorsqu'elle est sélectionnée dans la recherche et une seconde fois lorsqu'elle est ajoutée par défaut dans l'éditeur. Pour plus de détails, suivez ce guide étape par étape : https://www.loom.com/share/c019bda99f3a46019747efbcbfc73bd3
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 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: If you're experiencing issues with link arrays not showing in the Advanced Translation Screen, particularly with ACF blocks where the same label is used for multiple links or internal URLs are not visible, this summary might help. Solution: 1. When the same label, such as "Learn more", is used across several links in ACF blocks, they might share the same path attribute. WPML cannot register a string with the same path more than once, which results in only the last occurrence being shown in the translation editor. However, the translation will still apply correctly to all occurrences. 2. Internal URLs in blocks are hidden by default as WPML is designed to automatically translate these. If you need to see these URLs, you might be able to find them by searching within the translation editor. 3. For ACF link array fields, we recommend setting them to "translate" rather than "copy". This setting allows for manual editing of the URL if necessary, although WPML can automatically convert internal links.
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 issue persists, please open a new support ticket.
Problem: You are experiencing an issue where adding or editing content in a secondary language using WPML and the Avada Builder overwrites the content in the default language, and vice versa. Solution: We have identified that the issue arises from using both the WPML Advanced Translation Editor (ATE) and the WordPress/Avada editor simultaneously for translations. To resolve this, you should use only one method for translations. If you choose to continue with the WordPress/Avada editor, you need to disable the Advanced Translation Editor for the specific page or post. You can find instructions on how to do this here: Using Different Translation Editors for Different Pages. To ensure the solution works, please follow these steps: 1. Add the German text to the original (German) page. 2. Update the page. 3. Translate the content using WPML’s Advanced Translation Editor. 4. Check if the issue still occurs.
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 the issue persists, please open a new support ticket at WPML support forum.