Corrupted wp_options table
|Reported by:||gleuch||Owned by:||dd32|
|Severity:||normal||Keywords:||database installation corrupt-table|
Had the wp_options table become corrupted (unrepairable) in database on a very high-traffic, long-running, older blog. As WordPress could not read from this table, it trigger itself to run installation mode, thinking since wp_options cannot be read, it must be a new installation.
On a high-traffic site (rocketboom.com), some of our users decided to "help" us with this installation process, causing WordPress to overwrite content in wp_posts, replacing nearly 1000 posts & additional thousands of audits each with the "hello world" post. Additional post options/data remained, however title & body were altered. Of course, installation would fail since wp_options was still corrupted & unrepairable.
Reporting Bug & Suggested Solution: WordPress should not assume itself to be a new installation if tables exist but are corrupted. Installation mode should check if tables do exist, analyze, and if errors/corruption, trigger an error instead of attempting new installation.
Additional Suggested Features: Allow WordPress to attempt table repair, notify site owner, and display friendly error to viewers if any table is corrupted.
NB: Unable to test in newer versions since it was a production-side issue and specific plugins are locked to this version. If this is something that has been addressed in newer versions, please mark accordingly.