WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE gVnZr3_aipkit_content_writer_templates ( id bigint(20) unsigned NOT NULL AUTO_INCREMENT, user_id bigint(20) unsigned NOT NULL, template_name varchar(255) NOT NULL, template_type varchar(50) NOT NULL DEFAULT 'content_writer', config longtext NOT NULL, is_default tinyint(1) NOT NULL DEFAULT 0, created_at datetime NOT NULL DEFAULT CURRENT_TIMESTAMP, updated_at datetime NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, post_type varchar(20) DEFAULT 'post', post_author bigint(20) unsigned DEFAULT NULL, post_status varchar(20) DEFAULT 'draft', post_schedule datetime DEFAULT NULL, post_categories text DEFAULT NULL, PRIMARY KEY (id), UNIQUE KEY user_template_name_type (user_id, template_name, template_type), KEY user_id (user_id), KEY template_type (template_type), KEY is_default (is_default), KEY post_type (post_type) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE gVnZr3_aipkit_rss_history ( id bigint(20) unsigned NOT NULL AUTO_INCREMENT, task_id bigint(20) unsigned NOT NULL, item_guid varchar(255) NOT NULL, processed_at datetime NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (id), UNIQUE KEY unique_task_guid (task_id, item_guid), KEY task_id (task_id) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci