Problem: The client was facing issues with translating the footer into French on their WordPress site. The English footer was appearing instead of the French one, despite attempts to edit it directly in the footer editor. Additionally, there was a PHP error related to the Complianz GDPR plugin, indicating that translation loading was triggered too early. Solution: We advised the client not to edit the translation directly from the footer editor but to use WPML > String Translation to manage footer translations. For the PHP error, it was identified as a known issue with a fix available in the newer version of the Complianz plugin. We provided links to the relevant documentation and updates:
We corrected the language settings for the footer strings from English to French to resolve the translation issue.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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 French Support Forum.
Problem: The client was experiencing a 503 error in WordPress when using WPML, along with a PHP Fatal error related to the function
get_requested_lang()
. After reinstalling WPML, a new error appeared regarding the premature loading of translations, indicated by the function
_load_textdomain_just_in_time
. Additionally, the client noted slow loading times in the WooCommerce settings when WPML was active. Solution: We identified that the issues were not directly caused by WPML but were related to the latest changes in the WordPress core and possibly other third-party plugins or themes. We recommended the following steps: 1. Check the errata page for known issues: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 2. Re-upload the WPML plugin to ensure all files are correctly installed. 3. Create a full site backup before making any changes. 4. If the problem persists, we recommended opening a new support ticket for further assistance.
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 at WPML support forum.
Problème : Vous utilisez le thème Twenty Twenty-Five avec un Page Builder pour modifier le modèle de catégorie de votre livre en anglais, mais vous rencontrez des difficultés pour lier ce modèle à la page en français en modifiant les taxonomies. Le modèle de catégorie ne se reflète pas correctement dans la traduction française, résultant en l'affichage de la version générique des archives de catégorie.
Solution : Nous vous recommandons de suivre ces étapes pour résoudre le problème : 1. Supprimez la traduction de la base de données (wp_posts et icl_translations). 2. Activez la traduction du slug dans WPML > Paramètres (Page URL > Translate). Cela inclura le slug dans la traduction et ne le créera pas automatiquement à partir du titre. 3. Allez à : wp-content/plugins/sitepress-multilingual-cms/classes/full-site-editing/BlockTemplates.php et commentez la ligne suivante :
$postData['post_name'] = $post->post_name;
4. Envoyez le modèle à la traduction depuis le gestionnaire de traduction. 5. Assurez-vous que le slug traduit est correct, par exemple « category-exemple ».
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 vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si nécessaire, n'hésitez pas à ouvrir un nouveau ticket de support.
