Skip Navigation

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.

This topic contains 2 replies, has 1 voice.

Last updated by Andrey 2 months, 1 week ago.

Author Posts
December 17, 2024 at 3:22 pm #16522475

chetanP-4

Background of the issue:
I followed the steps in your email and updated the WPML Plugin to version 4.6.15 and then updated Elementor to version 3.26. We are still experiencing a Critical Error. The issue can be seen at: hidden link

Symptoms:
I am still receiving a Critical Error on the site after updating. Note that the site has been reverted to Version 4.6.14 until a solution is found.

Questions:
What should I do now?

December 17, 2024 at 3:23 pm #16522503

chetanP-4

Making sure you receive the support information.

December 17, 2024 at 10:47 pm #16523709

Andrey
Supporter

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+02:00)

While one of my teammates takes care of your ticket, I will provide you with the first debugging steps.

You need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debug. You can do this by adding a few lines to the site’s wp-config.php file. With error log enabled, you will see what the actual problem is.

To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:

define('WP_DEBUG', true);

In order 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 );

In this case, the errors will be saved to a debug.log log file inside the /wp-content/directory.

https://wpml.org/documentation/support/debugging-wpml/

Let us know what you see after the debug mode has been enabled.

The topic ‘[Closed] Critical Error after Updating to Version 4.6.15’ is closed to new replies.