Title: WordPress database error Specified key was too long;
Last modified: July 2, 2026

---

# WordPress database error Specified key was too long;

 *  Resolved [zebralove](https://wordpress.org/support/users/zebralove/)
 * (@zebralove)
 * [4 days, 6 hours ago](https://wordpress.org/support/topic/wordpress-database-error-specified-key-was-too-long-3/)
 * Starting on July 1st we started seeing the following error in our error log basically
   every minute.
 * WordPress database error Specified key was too long; max key length is 1000 bytes
   for query CREATE TABLE wpgx_hcaptcha_events ( id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
   source VARCHAR(256) NOT NULL, form_id VARCHAR(20) NOT NULL, ip VARCHAR(39) NOT
   NULL, user_agent VARCHAR(256) NOT NULL, uuid VARCHAR(36) NOT NULL, error_codes
   VARCHAR(256) NOT NULL, date_gmt DATETIME NOT NULL, status VARCHAR(20) NOT NULL
   DEFAULT ‘active’, trashed_at_gmt DATETIME NULL, PRIMARY KEY (id), KEY source (
   source), KEY form_id (form_id), KEY hcaptcha_id (source, form_id), KEY ip (ip),
   KEY uuid (uuid), KEY date_gmt (date_gmt), KEY status_date_gmt (status, date_gmt),
   KEY status_source_form (status, source, form_id) ) DEFAULT CHARACTER SET utf8mb4
   COLLATE utf8mb4_unicode_520_ci made by require_once(‘wp-load.php’), require_once(‘
   wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/hcaptcha-
   for-forms-and-more/hcaptcha.php’), HCaptcha\Main->init, HCaptcha\Main->load, 
   HCaptcha\Migrations\Migrations->__construct, HCaptcha\Migrations\Migrations->
   init, HCaptcha\Migrations\Migrations->maybe_create_tables, HCaptcha\Admin\Events\
   Events::create_table, dbDelta

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [kaggdesign](https://wordpress.org/support/users/kaggdesign/)
 * (@kaggdesign)
 * [3 days, 18 hours ago](https://wordpress.org/support/topic/wordpress-database-error-specified-key-was-too-long-3/#post-18955027)
 * Hi [@zebralove](https://wordpress.org/support/users/zebralove/) ,
 * This issue is related to your database using MariaDB with the outdated MyISAM
   storage engine. MyISAM has a 1000-byte key length limit, and the current Events
   table indexes can exceed that limit when utf8mb4 is used.
 * We are aware of this issue, and it has already been fixed [here](https://github.com/hCaptcha/hcaptcha-wordpress-plugin/issues/487).
 * The fix will be included in version 5.1.0, which should be released in the next
   few days. If you would like to test it earlier, you can install v5.1.0-RC4 from
   [here](https://drive.google.com/file/d/1zv9eB_2STLjoc5PGaZLQpy3A8gduxe8Y/view?usp=drive_link).

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwordpress-database-error-specified-key-was-too-long-3%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/hcaptcha-for-forms-and-more/assets/icon.svg?rev=3026321)
 * [hCaptcha for WP](https://wordpress.org/plugins/hcaptcha-for-forms-and-more/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/hcaptcha-for-forms-and-more/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/hcaptcha-for-forms-and-more/)
 * [Active Topics](https://wordpress.org/support/plugin/hcaptcha-for-forms-and-more/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/hcaptcha-for-forms-and-more/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/hcaptcha-for-forms-and-more/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [kaggdesign](https://wordpress.org/support/users/kaggdesign/)
 * Last activity: [3 days, 18 hours ago](https://wordpress.org/support/topic/wordpress-database-error-specified-key-was-too-long-3/#post-18955027)
 * Status: resolved