Skip Navigation

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

Problem:
The client was experiencing a critical error on their site after purchasing and attempting to activate WPML. The error persisted even after deactivating all other plugins and switching to the default WordPress theme.

Solution:
We identified that the issue was due to corrupted default WordPress tables, specifically missing auto increments in the

wp_users

,

wp_usermeta

, and

wp_options

tables, with many entries having an ID of '0'. We provided a solution that involved running SQL queries to delete the bad data and alter the tables to add the necessary auto increments. The client needed to execute the following queries one by one:

DELETE FROM `wp_users` WHERE `ID` = '0';

ALTER TABLE `wp_users` CHANGE `ID` `ID` bigint unsigned NOT NULL AUTO_INCREMENT FIRST;

DELETE FROM `wp_usermeta` WHERE `umeta_id` = '0';

ALTER TABLE `wp_usermeta` CHANGE `umeta_id` `umeta_id` bigint unsigned NOT NULL AUTO_INCREMENT FIRST;

DELETE FROM `wp_options` WHERE `option_id` = '0';

ALTER TABLE `wp_options` CHANGE `option_id` `option_id` bigint unsigned NOT NULL AUTO_INCREMENT PRIMARY KEY FIRST;

We advised the client to back up their database before making any changes. If the client was not comfortable performing these steps or if the solution did not resolve the issue, we recommended seeking further assistance, as this was beyond the scope of our support.

Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If you're still facing issues, 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 the problem persists, please open a new support ticket with us.

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: 

This topic contains 22 replies, has 2 voices.

Last updated by Andrey 1 year, 1 month ago.

Assisted by: Andrey.

Author Posts
April 30, 2024 at 4:17 am #15579152

adityaK-4

Please update on whats going on...

April 30, 2024 at 8:44 am #15579974

Andrey
WPML Supporter since 06/2013

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

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

I will update you as soon as I have more news. Thank you for your patience.

May 1, 2024 at 6:38 am #15583158

adityaK-4

Hi, how are you...
is there any update about the issue, please update as soon as you fix the issue

thanks.

May 1, 2024 at 8:57 am #15583413

Andrey
WPML Supporter since 06/2013

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

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

Hello,

I wanted to let you know that I have forwarded the issue you reported to our team. I will keep you updated on any progress.

Thank you for your patience.

May 2, 2024 at 11:54 am #15586971

adityaK-4

Hi, How are you

My website traffic is really going down because of this error. I currently i am facing this issue continuously. please update about this soon...

May 3, 2024 at 9:37 am #15590582

Andrey
WPML Supporter since 06/2013

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

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

I appreciate your patience.

We have reviewed the problem you reported and found that the issue with WPML is happening because your default WordPress tables seem to be corrupted. The wp_users, wp_usermeta, and wp_option tables are missing auto increments. You have many entries with ID 0, which is incorrect.

We can suggest a simple fix, but this requires deleting bad data. We cannot guarantee that this will not affect your site.

You ran the following queries one by one:

DELETE FROM `wp_users`
WHERE `ID` = '0';


ALTER TABLE `wp_users`
CHANGE `ID` `ID` bigint unsigned NOT NULL AUTO_INCREMENT FIRST;


DELETE FROM `wp_usermeta`
WHERE `umeta_id` = '0';


ALTER TABLE `wp_usermeta`
CHANGE `umeta_id` `umeta_id` bigint unsigned NOT NULL AUTO_INCREMENT FIRST;

DELETE FROM `wp_options`
WHERE `option_id` = '0';

ALTER TABLE `wp_options`
CHANGE `option_id` `option_id` bigint unsigned NOT NULL AUTO_INCREMENT PRIMARY KEY FIRST;

If this does not work or you need another way to fix the WP tables, you need someone to help you with this step, as this is beyond the support provided here.

Before proceeding with any changes, please back up your database first.

May 6, 2024 at 10:34 am #15596551

adityaK-4

Hi, i did as you said and these queries executed successfully. but after that when i try to install the WPML plugin manually it is working for few second and then after few seconds when i reload its showing the same critical error.

and i checked the error_log. there showing:

Cron reschedule event error for hook: action_scheduler_run_queue, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}

this is the log i get.

May 6, 2024 at 12:01 pm #15597152

Andrey
WPML Supporter since 06/2013

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

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

Thank you for your feedback. The error seems to be unrelated to WPML. It could related to:

https://wordpress.org/support/topic/cron-jobs-related-error-cron-reschedule-event-error/

https://core.trac.wordpress.org/ticket/57271

https://core.trac.wordpress.org/ticket/56048