• Resolved hbk747

    (@hbk747)


    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 an ALTER TABLE query on the kqd_mlw_results table to add a new UNIQUE key, 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_results table.

    Thank you for your prompt attention to this urgent matter.

    Warm regards,

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • dhanush22

    (@dhanush22)

    Dear @hbk747 ,

    I hope you’re doing great. Thank you for reaching out to us.

    I wanted to let you know that the issue you reported has been shared with our development team for further review and has been marked as a high priority. We’ll continue to post updates directly in this support thread as soon as we have more information.

    Apart from this issue, if there’s anything else you’d like to discuss, please feel free to share it here so we can continue different conversations within this same thread.

    Thank you for your time and cooperation.

    Best regards,
    Dhanush

Viewing 1 replies (of 1 total)

The topic ‘Fatal Database Error (WSOD) on admin_init – “Too many keys specified’ is closed to new replies.