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.
Problem: The client wants the Chinese language option on their website to redirect users to an external Chinese website, instead of showing a translated version of the current site. They tried to manually add the external link to the Language Menu, but it didn't work as WPML controls the language menu rendering. Solution: We explained that WPML's language switcher is designed to switch between languages managed within the site by WPML and does not support linking directly to external sites. To achieve the desired functionality, the client needs to manually add the external link using a page builder or other WordPress tools.
If this solution does not apply to your case, or if it seems outdated, 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: If you're experiencing issues with the WPML translation where clicking the translate button redirects you back to the page with an authentication error, and you also encounter a 'too many redirects' error, the problem might be related to custom code in your site's functions.php file. Solution: We recommend checking the functions.php file in your website's Child Theme for any custom code that might be modifying the redirect request and causing a signature mismatch. If the issue disappears when the parent theme is enabled, this indicates that the problematic code is in the Child Theme's functions.php. You should remove the code blocks one by one to identify which one is causing the issue.
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 at WPML support forum.
Problem: You are experiencing a loss of metadata, specifically translator comments from XLIFF files, when switching from the Advanced Translation Editor to the standard WordPress editor. This issue arises after clicking "Edit anyway", causing the translation to disconnect from the XLIFF file and resulting in the loss of all translator comments. Solution: Unfortunately, it is technically not possible with WPML to maintain the
<note>
elements from XLIFF files once you switch to the native WordPress editor. Custom development would be necessary to import these
<note>
elements into WordPress metadata or to make them visible in the block editor UI. We recommend setting the translation method on the original content to "WordPress Editor" to prevent overwriting manual translations when later using the WPML Translation Editor. For more details on setting the translation method, please visit: Using different translation editors for different pages.
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 further assistance is needed, please open a new support ticket at WPML support forum.
