Problème : Après une mise à jour, un bug est apparu dans une page Divi traduite en quatre langues via WPML. Seul le contenu en allemand s'affiche correctement, les autres langues restent en allemand malgré le changement de langue. Solution : Il semble que les identifiants de shortcode n'ont pas été traduits ou que Divi a changé la manière de gérer ces traductions. Nous recommandons de traduire manuellement les identifiants de shortcode comme montré dans les captures d'écran fournies par notre équipe. Après la traduction, il est important de supprimer le cache du site et de WPML pour que les modifications prennent effet.
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, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et si nécessaire, de ouvrir un nouveau ticket de support.
Problem: After migrating a multi-lingual site to a new production server, the backend became very slow, primarily due to frequent API calls made by the WPML Multilingual CMS plugin, resulting in '426 Upgrade Required' errors. Solution: First, ensure that all WPML plugins are updated to their latest versions. Next, within the WPML settings, switch the translation editor as this might resolve the issue temporarily. Additionally, check WPML logs for repeated API requests and review server resource usage to identify any loops or redundant external calls. If these steps do not alleviate the problem, it may be due to a bug that our developers are currently investigating. In this case, switching the translation editor as per the instructions in WPML → Settings should serve as a temporary workaround.
Please note that this solution might become outdated or may not apply to your specific situation. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please do not hesitate to open a new support ticket.
Problem: If you're experiencing issues with WooCommerce endpoints showing a 404 error on your multilingual site, particularly when switching languages, and it temporarily resolves by flushing permalinks but reoccurs, this might be relevant to you. Solution: We recommend updating your WPML Multilingual & Multicurrency for WooCommerce to version 5.5.4 once it is released, as it includes a fix for this issue. Ensure you always have the latest version installed. If this solution becomes outdated or does not resolve your specific case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing a fatal error with WPML when another plugin tries to read the configuration of your shop, and you're using PHP 8.4, this might be due to deprecated warnings triggered by the new checks introduced in PHP 8.4. Solution: We recommend switching to a PHP version prior to 8.4 as a temporary workaround while we address these compatibility issues. This change should help avoid the fatal error you're encountering.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, we highly recommend checking related 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.
Problem: If you're experiencing warnings and a 404 page after using the autotranslate feature on your site, particularly when switching to languages like Danish, and your theme is compatible with WPML, the issue might be related to your site settings. Solution: We discovered that although the Settings → General page displayed values for both Site URL and Home URL, the Home URL was actually empty in the database (in the wp_options table). This mismatch was likely causing the problem. Simply re-saving the settings page might not repopulate the value due to the issue itself preventing it. Therefore, we recommend updating the Home URL directly in the database. After making this change, please check your site to confirm that everything is working as expected.
This solution might be irrelevant if it's 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. If the problem persists, please open a new support ticket.
