WordPress database error: [Cannot add foreign key constraint]CREATE TABLE IF NOT EXISTS wp_kirki_stages (
id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT,
post_id BIGINT(20) UNSIGNED NOT NULL,
type VARCHAR(50) NOT NULL DEFAULT 'page',
version BIGINT(20) UNSIGNED NOT NULL,
name VARCHAR(255) NOT NULL DEFAULT '',
edited_by BIGINT(20) UNSIGNED NOT NULL DEFAULT 0,
is_published TINYINT(1) NOT NULL DEFAULT 0,
no_legacy_global_style TINYINT(1) NOT NULL DEFAULT 0,
created_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (id),
UNIQUE KEY post_version (post_id, version),
KEY post_id (post_id),
KEY post_published (post_id, is_published),
FOREIGN KEY (post_id) REFERENCES wp_posts(ID) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
WordPress database error: [Cannot add foreign key constraint]CREATE TABLE IF NOT EXISTS wp_kirki_stage_data (
id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT,
stage_id BIGINT(20) UNSIGNED NOT NULL,
meta_key VARCHAR(191) NOT NULL,
meta_value LONGTEXT NULL,
PRIMARY KEY (id),
UNIQUE KEY stage_meta_key (stage_id, meta_key),
FOREIGN KEY (stage_id) REFERENCES wp_kirki_stages(id) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci
patchstack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/sustafrm/public_html/managementnext.com/wp-includes/functions.php on line 6260