Bug

Problem:
The client is testing the migration from Divi 4 to Divi 5 locally and encountered a WPML message unsure how to respond, thinking local testing wouldn't affect anything.
Solution:
We understand the situation and it's great to test major updates like Divi 4 to Divi 5 on a local or staging site. The WPML message seen in the local environment is likely related to translation services communications, which can create inconsistencies with the actual production site. To prevent the test site from interfering with the translation services of the production site, we can instruct WPML that this environment is solely for testing purposes. This will block critical requests to translation services.
Here are the steps to follow:
1. **Access the

wp-config.php

file of your local site.** You can find it at the root of your WordPress installation, accessible via your local file manager or a code editor.
2. **Add the following line of code** just before the line `/* That's all, stop editing! Happy blogging. */` (or equivalent):

define( 'WPML_ENVIRONMENT', 'test' );

This should look like this:

define( 'WPML_ENVIRONMENT', 'test' );<br /><br />/* That's all, stop editing! Happy blogging. */

3. **Save the changes** made to the

wp-config.php

file.
After adding this line, the local site should no longer attempt to interfere with the translation services, and the WPML message should disappear. Could you try this and let us know if the message persists?

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. If the problem persists, please open a new support ticket.

Problem:
The client was experiencing issues with 'ghost' templates in the database that were overwriting translations in a multilingual website setup using WPML and Divi. This problem was particularly affecting the French language version of the site.
Solution:
We manually inspected the database and the Divi Library to identify and exclude non-matching templates that were causing the issue. After identifying these 'ghost' templates, we removed them to resolve the conflict. This process was necessary for other languages as well, and we are currently working to ensure all language versions are corrected. If you're experiencing similar issues, we recommend checking for discrepancies between your database entries and your theme's library, and removing any conflicting templates.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the 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:
Vous rencontrez une erreur critique sur votre site après avoir activé la détection automatique des images et des médias dans WPML. Vous avez tenté de restaurer votre site et de désactiver les plugins WPML via SFTP, mais l'erreur réapparaît lors de la réactivation de WPML Multilingual CMS.
Solution:
1. Assurez-vous que les extensions DOM et XML PHP sont activées sur votre serveur. Ces extensions sont nécessaires pour le bon fonctionnement de WPML.
2. Pour activer ces extensions, vous pouvez modifier le fichier php.ini de votre serveur. Si vous n'êtes pas sûr de la procédure, il est recommandé de contacter votre fournisseur d'hébergement pour qu'il effectue cette modification.
3. Pour aider à diagnostiquer et résoudre le problème, activez le journal de débogage de WordPress en modifiant votre fichier wp-config.php comme suit:

define('WP_DEBUG', true);<br />define('WP_DEBUG_LOG', true);<br />define('WP_DEBUG_DISPLAY', false);<br />@ini_set('display_errors',0);

4. Après avoir effectué ces modifications, tentez de reproduire le problème et vérifiez si des erreurs sont enregistrées dans le fichier debug.log.
Si ces étapes ne résolvent pas le problème ou si vous avez besoin d'assistance supplémentaire, nous vous recommandons de consulter les problèmes connus et de vérifier 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.