Problem: The client was experiencing issues with WPML on their site after adding a card for unlimited translation. This led to the disappearance of the "translator" page and a request for a key for a translation service. Despite deactivating everything, performing a hard reset, and cleaning database tables and options related to WPML, the problem persisted. The client also noted a JavaScript file that was blocking the page. Solution: We suggested verifying if both sites (production and development) were hosted on the same server with identical CDN, dependencies, and firewall configurations. We recommended trying an older version of WPML, specifically version 4.8.6, which can be downloaded from here. If this version worked, the client could then update to the newer version. Additionally, we advised checking the WPML > Support > Installer debug to ensure the API was connected properly.
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.
Problem: You are encountering a database error after migrating your domain to a new hosting environment. The error is caused by an emoji in a WooCommerce translation string, which leads to a query failure due to mixed collation in the database. Solution: We recommend removing the emoji from the content as a temporary workaround. If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, feel free to open a new support ticket at our support forum.
Problem: If you're experiencing a fatal error when trying to activate the WPML plugin, it might be due to an issue with your MySQL version. The error message indicates a problem with creating a table because only one TIMESTAMP column with CURRENT_TIMESTAMP in the DEFAULT or ON UPDATE clause is allowed. Solution: We recommend updating your MySQL to the latest stable version supported by your hosting environment. This issue often occurs with MySQL versions ≤ 5.5 or early versions of 5.6, which only allow one TIMESTAMP column with DEFAULT CURRENT_TIMESTAMP or ON UPDATE CURRENT_TIMESTAMP per table. Updating MySQL should resolve this issue. Additionally, consider updating PHP to the latest supported version to enhance performance, security, and compatibility with modern plugins.
If this solution does not apply to your case, or if it seems outdated, please check the related 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.
Problème : Après la mise à jour des plugins WPML, une erreur de base de données empêche les modifications sur le site, indiquant un problème avec la définition de la table et l'utilisation de plusieurs colonnes TIMESTAMP avec CURRENT_TIMESTAMP. Solution : Nous vous recommandons de vérifier la version de votre base de données MySQL. Cette erreur peut survenir avec les versions antérieures à MySQL 5.6. Pour vérifier votre version actuelle, allez dans Outils > Santé du site > Infos, et consultez la section Base de données. Si vous utilisez une version obsolète, nous vous conseillons de mettre à jour votre base de données MariaDB ou MySQL vers la dernière version disponible.
Si cette solution ne résout pas votre problème ou si elle semble obsolète, nous vous recommandons de consulter les problèmes connus, de vérifier la version du correctif permanent et de vous assurer 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.
