Fatal Database Error (WSOD) on admin_init – “Too many keys specified
-
Hello,
I emailed you as well but did not hear from you. Usually, you guys reply super-fast there.
I am writing to report a critical database error occurring on my live production site, ParadigmShift.com.pk. that is causing a White Screen of Death (WSOD) when attempting to load the admin area. This issue appears to be related to an attempt by the QSM plugin to alter a database table during the WordPress initialization process.
The server log shows a specific MySQL error indicating a key limit violation when the plugin attempts to add a unique index.
This is the log:
[proxy_fcgi:error [pid 1838020:tid 1838327 [client 103.244.174.191:0 AH01071: Got error 'PHP message: WordPress database error Too many keys specified; max 64 keys allowed for query ALTER TABLE kqd_mlw_results ADD UNIQUE (unique_id) made by do_action('admin_init'), WP_Hook->do_action, WP_Hook->apply_filters, QSM_Install->update, MLWQuizMasterNext->wpdb_alter_table_query'The Core Problem: The database server (likely MySQL or MariaDB) is enforcing a limit of 64 keys/indexes per table. The plugin’s update/install routine (
MLWQuizMasterNext->wpdb_alter_table_query) attempts to run anALTER TABLEquery on thekqd_mlw_resultstable to add a newUNIQUEkey, but the table has already reached the 64-key limit, causing the query to fail and the entire WordPress script to halt.I asked Cloudways and they also confirmed that this is causing the issue. I had to deactivate the plugin.
I request that your development team investigate this issue immediately. This seems to be a conflict where your installation routine does not account for existing high key counts on the
kqd_mlw_resultstable.Thank you for your prompt attention to this urgent matter.
Warm regards,
The page I need help with: [log in to see the link]
The topic ‘Fatal Database Error (WSOD) on admin_init – “Too many keys specified’ is closed to new replies.