WordPress Database Error

  • Resolved Ken Sim

    (@kwsim539)


    1 year, 7 months ago

    On every website I install this plugin, I receive this error in my error logs. Then I receive a WordPress database error Table every time I save the settings because this wp_asenha_failed_logins table doesn’t exist.

    [30-Jul-2023 00:39:19 UTC] WordPress database error Specified key was too long; max key length is 1000 bytes for query CREATE TABLE wp_asenha_failed_logins (
    ip_address varchar(255) NOT NULL DEFAULT ”,
    username varchar(255) NOT NULL DEFAULT ”,
    fail_count int(10) NOT NULL DEFAULT ‘0’,
    lockout_count int(10) NOT NULL DEFAULT ‘0’,
    request_uri varchar(255) NOT NULL DEFAULT ”,
    unixtime int(10) NOT NULL DEFAULT ‘0’,
    datetime_wp varchar(255) NOT NULL DEFAULT ”,
    — datetime_utc datetime NULL DEFAULT CURRENT_TIMESTAMP,
    info varchar(255) NOT NULL DEFAULT ”,
    UNIQUE (ip_address)
    )
    DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci made by activate_plugin, do_action(‘activate_admin-site-enhancements/admin-site-enhancements.php’), WP_Hook->do_action, WP_Hook->apply_filters, asenha_on_activation, ASENHA\Classes\Activation->create_failed_logins_log_table, dbDelta

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Bowo

    (@qriouslad)

    @kwsim539 thanks for reporting, will investigate.

    What kind of hosting / server set up are you using? Can you provide more info on the database engine/version in use? You can use my other plugin, System Dashboard to check that.

    Thread Starter Ken Sim

    (@kwsim539)

    I’m not sure if you received my reply via email, because it was not posted here.

    I’m using my own VPS, (Apache v2.4.57 | Linux v3.10.0-1160.53.1.vz7.185.3).

    The database is MariaDB version 10.3.39

    Plugin Author Bowo

    (@qriouslad)

    @kwsim539 thank you . I recall you’ve been using ASE for a while Did the error appear since the first time you activated it, or, after a recent update (to ASE)?

    Thread Starter Ken Sim

    (@kwsim539)

    @qriouslad yes. I have been using this for a while, but I never used this feature because my security plugin handles this feature. It wasn’t noticed until I installed this on another website and tried to setup the SMTP. When I was using the Test Email, the spinner never stop. It didn’t return an error after a good 30 seconds. So, I checked the error log to see if there was a reason for this issue and then is when I found this error. I eventually figured out that the SMTP test issue was due to the SMTP password was incorrect.

    I uninstalled and reinstalled the plugin. As soon as I activated the plugin, the error happened again.

    Then I went back to the error logs of my other sites and found the same error. Along with all the “WordPress database error Table” for every time I saved the settings.

    • This reply was modified 1 year, 7 months ago by Ken Sim.
    Plugin Author Bowo

    (@qriouslad)

    @kwsim539 got it. Thanks for the detailed and helpful info. I’ll try to debug and fix in the next release.

    Plugin Author Bowo

    (@qriouslad)

    @kwsim539 this looks like it’s caused by an older version of MariaDB having lower limit of “key length” for the character set in use.

    Please try installing the hotfix at https://bowo.io/wp-content/uploads/2023/07/admin-site-enhancements.zip. If it solves the errors, I’ll include the fix in the next official release.

    Thread Starter Ken Sim

    (@kwsim539)

    That worked!

    1. I overwrote the plugin (No Error)
    2. Deactivated and Reactivated the plugin (No Error)
    3. Saved the settings (No Error)
    4. Verified that the ‘wp_asenha_failed_logins’ table was created

    Thanks for all your hard work. This call for another cup of coffee. LOL!

    Plugin Author Bowo

    (@qriouslad)

    @kwsim539 great to hear that! I’ve just released the fix as part of v5.4.1. Thanks for being a monthly sponsor of my work Ken!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘WordPress Database Error’ is closed to new replies.