Database issue after update

repair your database using phpmyadmin: https://www.a2hosting.com/kb/cpanel/cpanel-database-features/optimizing-and-repairing-mysql-databases-with-phpmyadmin

Hi Steve,

Thanks for your assistance. I have installed phpmyadmin and connected to my remote database server. I followed the guide, but its not working. Do i need to be logged in as root to the db or is the wordpress user in wp-config.php enough?

I got these errors…

The storage engine for the table doesn’t support r…

How and why did the latest woocommerce update drop my options table, i am confused.

I just tried it as db root and same thing. Looking into the error, this is because we use innodb? I am not sure where to go from here

Okay i found the tables were renamed back to old wp_ so i renamed them and now i have a new error:

wp_yOlG6f_actionscheduler_actions: Table ‘litldb.wp_yOlG6f_actionscheduler_actions’ doesn’t exist
wp_yOlG6f_actionscheduler_claims: Table ‘litldb.wp_yOlG6f_actionscheduler_claims’ doesn’t exist
wp_yOlG6f_actionscheduler_groups: Table ‘litldb.wp_yOlG6f_actionscheduler_groups’ doesn’t exist
wp_yOlG6f_actionscheduler_logs: Table ‘litldb.wp_yOlG6f_actionscheduler_logs’ doesn’t exist

You should have not renamed anything. The “error” from PHPMYADMIN was merely an informational message.

At this point, it’s probably best just to restore your database from a backup.

I didnt

The tables got renamed months before all this happened by a security plugin from WPMU Dev

I instead restored the db backup to a new instance, exported the missing tables and imported them into the broken DB and its working. But my REST API is now playing up and background processing appears to be off and i have no way to get it to do loopback background processing.

Any ideas? Much appreciated in advance

I only set the names back to how they was which wasnt wp_

The REST API encountered an unexpected result Performance
The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

The REST API call gave the following unexpected result: (500) {“capabilities”:{“edit_post”:”edit_post”,”read_post”:”read_post”,”delete_post”:”delete_post”,”edit_posts”:”edit_posts”,”edit_others_posts”:”edit_others_posts”,”publish_posts”:”publish_posts”,”read_private_posts”:”read_private_posts”,”read”:”read”,”delete_posts”:”delete_posts”,”delete_private_posts”:”delete_private_posts”,”delete_published_posts”:”delete_published_posts”,”delete_others_posts”:”delete_others_posts”,”edit_private_posts”:”edit_private_posts”,”edit_published_posts”:”edit_published_posts”,”create_posts”:”edit_posts”},”description”:””,”hierarchical”:false,”viewable”:true,”labels”:{“name”:”Posts”,”singular_name”:”Post”,”add_new”:”Add New”,”add_new_item”:”Add a New Post”,”edit_item”:”Edit