Problem: The client was experiencing a 500 Internal Server Error when trying to access
admin-ajax.php
. The error log indicated a fatal error in the WPML plugin file
sitepress.class.php
. The issue was resolved when the WPML plugin was deactivated. Solution: We recommended the client to deactivate the WP Query Monitor plugin and then reactivate WPML to check if the fatal error persists. This step was suggested as a potential conflict with a third-party plugin could cause the error.
If you're experiencing a similar issue, we recommend trying the following steps: 1. Deactivate any third-party plugins that may conflict with WPML. 2. Reactivate WPML and check if the error still occurs.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.
Problem: The client is experiencing a PHP Fatal error related to the WPML plugin after an upgrade, which is causing issues on various pages of their multilingual site. Solution: We recommend downloading fresh copies of the WPML plugins and updating them manually. Here are the steps to follow: 1. Visit the WPML downloads section to get the latest versions of the WPML plugins. 2. Follow the instructions on how to manually update WPML to proceed with the update. 3. Ensure to backup your database before starting the update process to prevent any data loss.
Problem:
Languages on the client's website were not mapped.
Solution:
The issue was that the site was "moved". Site moved is a permanent move, and WPML will be deactivated on the original site (which shouldn't exist anymore). That's why languages weren't mapped anymore.
You can revert the site to the original URL using the last link in the banner "indicate that this site should be at..."
