Wordpress crash

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is unable to log in to WordPress after updating to version 4.7 or higher. The error message indicates that some WPML components are not updated, specifically mentioning that 'sitepress-multilingual-cms' needs to be version 4.7.0.
Solution:
We recommend updating all WPML plugins to their latest versions. First, disable and delete the current WPML plugins, then download and install fresh copies from the 'My Account -> Downloads' section on our website. Ensure you also update your WordPress to the latest version. For detailed instructions on updating WPML, visit http://wpml.org/faq/install-wpml/.
Next, enable debugging to identify any specific errors. Modify your wp-config.php file by changing:

define('WP_DEBUG', false);

define('WP_DEBUG', true);

Also, add:

define('WP_DEBUG_LOG', true);

This will save error logs to a debug.log file in your /wp-content/ directory. For more on debugging WPML, visit https://wpml.org/documentation/support/debugging-wpml/.
Always ensure to back up your database before proceeding with these updates.

If this solution does not resolve your issue or seems outdated, please check for 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 problems persist, we highly recommend opening a new support ticket for further assistance.

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.

Tagged: Exception

This topic contains 1 reply, has 0 voices.

Last updated by Andrey 1 month ago.

Assisted by: Andrey.

Author	Posts
April 10, 2025 at 3:05 pm #16919387
svenv-8	Background of the issue: I am trying to update WordPress to version 4.7 or higher, but it becomes impossible to log in after the update. I have to deactivate the plugin via DirectAdmin, log into WordPress, delete the plugin, and then reinstall an older version. However, using the older version results in a notification about outdated components. Symptoms: After logging in, I receive an error message from WordPress. The notification states: 'You are running updated gravityforms-multilingual and wpml-string-translation, but the following components are not updated: sitepress-multilingual-cms (required version: 4.7.0). Your site will not work as it should in this configuration. Please update all components which you are using.' Questions: How can I resolve the login issue after updating to version 4.7 or higher? What steps should I take to update all components without causing errors?
April 10, 2025 at 7:30 pm #16920363
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for contacting WPML support. First, you need to ensure that you update all WPML plugins to their latest versions. You can disable WPML plugins, delete them, and upload freshly downloaded copies. You can check the latest released versions under "My Account -> Downloads" on the website. Instructions for updating can be found here: http://wpml.org/faq/install-wpml/. Next, make sure that your WordPress installation is also updated to the latest version. If you are still receiving a fatal error, you need to identify the actual message of the error. The first step is to enable debugging. You can do this by adding a few lines to the site’s wp-config.php file. With debugging enabled, you will be able to see the actual problem in the error log. To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to: define('WP_DEBUG', true); To enable the error logging to a file on the server, you need to add yet one more similar line: define( 'WP_DEBUG_LOG', true ); The errors will be saved to a debug.log file inside the /wp-content/directory. https://wpml.org/documentation/support/debugging-wpml/ Please remember to backup your database before you proceed. Let me know if the issue persists after an update has been done.