This thread is resolved. Here is a description of the problem and solution.
Problem: Le client a rencontré une erreur fatale de type E_ERROR après avoir migré son site utilisant WPML d'un serveur de développement à un serveur de production. L'erreur indiquée était 'Uncaught Error: Class "DOMDocument" not found' dans un fichier spécifique de WPML. Solution: Nous avons recommandé de vérifier si l'extension 'php-xml' était installée et activée dans la configuration PHP du serveur de production, car cette extension est nécessaire pour le fonctionnement correct de WPML. Nous avons également suggéré de vérifier si un plugin ou un thème tiers utilisait des fichiers XML mal configurés qui pourraient causer le problème.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de consulter les problèmes connus, de vérifier la version des correctifs permanents et de confirmer 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 sur notre forum de support.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
J'ai développé mon site sur mon serveur Siteground à l'adresse hidden link où WPML fonctionne sans problème. Le problème est survenu après avoir transféré mon site sur le serveur de production du client (cPanel) à l'adresse hidden link en utilisant MigrateGuru. J'ai désinstallé WPML et supprimé la clé WPML, puis tenté de refaire la migration en désactivant WPML sur le site source et en créant une nouvelle clé pour le site de destination, mais cela n'a pas fonctionné.
Symptoms:
J'ai une erreur fatale de type E_ERROR causée par la ligne 67 du fichier /home/ambianc1/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/xml-config/class-wpml-xml-config-validate.php. Message d'erreur : Uncaught Error: Class "DOMDocument" not found. Le back-end de WordPress plante sans arrêt sur le site de destination.
Questions:
Comment résoudre l'erreur fatale de type E_ERROR causée par WPML sur le serveur de production ?
Pourquoi WPML fonctionne-t-il sur le serveur de développement mais pas sur le serveur de production ?
While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly.
Can you please check with your hosting support that the 'php-xml' extension is installed and enabled in your PHP configuration? This extension is necessary for WPML to function correctly, as it relies on XML parsing.
There is a chance a third party plugin or theme is using misconfigured XML files that might be causing this issue.
In order to further debug I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)
**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **
I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.
NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.
Hi! Please, do not close the ticket. I will get back to you with the access information to the production website early this week (as this week-end was an holiday).
Hi Bobby! I won't need your help anymore as I decided to change the hosting service (other bug came) and WPML works well now.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.