Problem: When translating a page, no content appears translated, and the translation editor shows zero words. Solution: The issue was traced to custom code in the child theme that was preventing WPML scripts from loading correctly. We recommend switching to the parent theme to verify if the translation editor then functions properly and the content becomes visible for translation. If the issue resolves, review and possibly disable parts of the custom code in the child theme to isolate the exact cause. If further assistance is needed, we suggest visiting our support forum.
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.
Problème : Le client a rencontré un problème où la page principale ne s'affichait pas en version anglaise, malgré le fait que la page soit bien traduite. De plus, il y avait des erreurs dans le code PHP utilisé pour afficher des images, ce qui causait des problèmes de traduction et d'affichage des images en anglais.
Solution : Nous avons identifié que le problème provenait de l'utilisation incorrecte des champs ACF dans le code PHP, notamment avec l'utilisation de
$image1['url']
qui n'est pas sûr avec PHP 8.0 et versions ultérieures. Nous avons proposé une version améliorée du code pour gérer correctement les différents types de retours du champ 'Image' d'ACF (tableau, chaîne de caractères, entier). Voici le code corrigé :
Nous avons également recommandé de supprimer le fichier debug_log de 18 Go dans le dossier wp-content si le client n'en a plus besoin. Nous avons souligné que ce code est personnalisé et que normalement, nous ne fournissons pas d'assistance pour de tels cas. Le client ou son développeur doit s'assurer que le code ajouté est compatible avec 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 confirmer que vous avez installé les dernières versions des thèmes et plugins, et si nécessaire, d'ouvrir un nouveau ticket de support sur notre forum d'assistance.
Problem: The client is experiencing inconsistent page loading, sometimes resulting in a 500 error or a redirect loop on their multilingual site using WPML. This issue occurs after updating the Learndash plugin, but persists even after deactivating other plugins like Memberium, suggesting a problem with WPML’s language routing or translation handling. Solution: We recommend reviewing the WPML configuration for the affected page, particularly its translation status, language assignment, and URL structure. Additionally, try the following workaround: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/
If this solution does not resolve the 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: If you're experiencing issues where the 'My Account > My Courses' page only works in English and redirects to the 'My Account' page in other languages, it might be due to incorrect URL handling in your custom theme. Solution: We recommend checking the
functions.php
file in your theme. Specifically, look for the function that customizes the WooCommerce menu on the 'My Account' page. You might find that the URL is hardcoded to 'my-account/my-courses', which does not account for language variations. Replace:
This change should correct the URL to reflect the appropriate language-specific endpoint. Please ensure to backup your database and website before making any changes.
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.
Problem: If you're experiencing issues with a pure HTML block that contains a contact form, such as
<div id="form-acm_55342"></div>
, not being detected in the Advanced Translation Editor (ATE) screen, we can help. Solution: We recommend using the custom XML configuration code below to inform WPML about the elements that need to be translated within your custom HTML code:
After adding this code to WPML > Settings > Custom XML Configuration, the form ID "form-acm_55342" should be available in ATE for translation. For more details, please visit our documentation on how to make custom Gutenberg blocks translatable.
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.
