Posted: January 26, 2017 at 5:41 am
Can anyone help me with this? WordPress databasefout: [Index column size too large. The maximum column size is 767 bytes.] Stack Trace:#0 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(727): EventEspresso\core\services\database\TableManager->createTable(‘esp_message’, ‘MSG_ID bigint(2…’, ‘InnoDB’) #1 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(557): EEH_Activation::create_table(‘esp_message’, ‘MSG_ID bigint(2…’, ‘ENGINE=InnoDB’, false) #2 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(430): EE_Data_Migration_Script_Base->_create_table_and_catch_errors(‘esp_message’, ‘MSG_ID bigint(2…’, ‘ENGINE=InnoDB’, false) #3 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_DMS_Core_4_9_0.dms.php(312): EE_Data_Migration_Script_Base->_table_is_new_in_this_version(‘esp_message’, ‘MSG_ID bigint(2…’, ‘ENGINE=InnoDB’) #4 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(850): EE_DMS_Core_4_9_0->schema_changes_before_migration() #5 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(125): EEH_Activation::create_database_tables() #6 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(374): EEH_Activation::initialize_db_and_folders() #7 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/admin_pages/maintenance/Maintenance_Admin_Page.core.php(506): EE_System->initialize_db_if_no_migrations_required(true) #8 [internal function]: Maintenance_Admin_Page->_reset_db(true) #9 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(865): call_user_func_array(Array, Array) #10 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(681): EE_Admin_Page->_route_admin_request() #11 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(532): EE_Admin_Page->route_admin_request() #12 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(200): EE_Admin_Page->_page_setup() #13 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/admin_pages/maintenance/Maintenance_Admin_Page.core.php(33): EE_Admin_Page->__construct(true) #14 [internal function]: Maintenance_Admin_Page->__construct(true) #15 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Init.core.php(392): ReflectionClass->newInstance(true) #16 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Init.core.php(267): EE_Admin_Page_Init->_initialize_admin_page() #17 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Loader.core.php(342): EE_Admin_Page_Init->do_initial_loads() #18 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_Loader.core.php(120): EE_Admin_Page_Loader->_get_installed_pages() #19 [internal function]: EE_Admin_Page_Loader->__construct() #20 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(884): ReflectionClass->newInstanceArgs(Array) #21 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(687): EE_Registry->_create_object(‘EE_Admin_Page_L…’, Array, ‘core’, false) #22 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(360): EE_Registry->_load(Array, ‘EE_’, ‘Admin_Page_Load…’, ‘core’, Array, false, true, false) #23 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin.core.php(191): EE_Registry->load_core(‘Admin_Page_Load…’) #24 [internal function]: EE_Admin->init(”) #25 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array) #26 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array) #27 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #28 /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(943): do_action(‘AHEE__EE_System…’) #29 [internal function]: EE_System->initialize_last(”) #30 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array) #31 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array) #32 /home/deb73553n2/domains/nlsas.nl/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #33 /home/deb73553n2/domains/nlsas.nl/public_html/wp-settings.php(449): do_action(‘init’) #34 /home/deb73553n2/domains/nlsas.nl/public_html/wp-config.php(90): require_once(‘/home/deb73553n…’) #35 /home/deb73553n2/domains/nlsas.nl/public_html/wp-load.php(37): require_once(‘/home/deb73553n…’) #36 /home/deb73553n2/domains/nlsas.nl/public_html/wp-admin/admin.php(31): require_once(‘/home/deb73553n…’) #37 {main} WordPress databasefout: [Table ‘deb73553n2_wp1.wp_esp_message’ doesn’t exist] Thanks! |
|
Hi Wim, Can you contact your host and ask them to enable larger index columns by enabling the innodb_large_prefix setting? Reference: |
|
innodb_large_prefix = ON , innodb_file_format = BARRACUDA, |
|
If you need more info or want connection to phpmyadmin, please let me know. It would be very helpful to have this problem solved. Now I cannot deliver a working EE4. Wim |
|
Did the settings require a change? If so, was the database server rebooted? |
|
No, I think not. |
|
I did an experiment in phpmyadmin with the same syntax but with extra ROW_FORMAT=DYNAMIC. Then the table gave no error. |
|
Did the wp_esp_message table end up getting created then? |
|
Yes it was created then manually. |
|
I managed to create wp_esp_message table manually with ROW_FORMAT=COMPRTESSED. But when I add an event it says: Notice: WPDB Error “Table ‘deb73553n2_wp1.wp_esp_attendee_meta’ doesn’t exist” tijdens het uitvoeren van wpdb methode “get_results” met argumenten [“SELECT Registration.REG_ID AS ‘Registration.REG_ID’, Registration.EVT_ID AS ‘Registration.EVT_ID’, Registration.ATT_ID AS ‘Registration.ATT_ID’, Registration.TXN_ID AS ‘Registration.TXN_ID’, Registration.TKT_ID AS ‘Registration.TKT_ID’, Registration.STS_ID AS ‘Registration.STS_ID’, Registration.REG_date AS ‘Registration.REG_date’, Registration.REG_final_price AS ‘Registration.REG_final_price’, Registration.REG_paid AS ‘Registration.REG_paid’, Registration.REG_session AS ‘Registration.REG_session’, Registration.REG_code AS ‘Registration.REG_code’, Registration.REG_url_link AS ‘Registration.REG_url_link’, Registration.REG_count AS ‘Registration.REG_count’, Registration.REG_group_size AS ‘Registration.REG_group_size’, Registration.REG_att_is_going AS ‘Registration.REG_att_is_going’, Registration.REG_deleted AS ‘Registration.REG_deleted’, TransactionTable.TXN_ID AS ‘Transact in /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2263 Notice: WPDB AGAIN: Fout “Table ‘deb73553n2_wp1.wp_esp_attendee_meta’ doesn’t exist” tijdens het uitvoeren van dezelfde methode en argumenten als eerder. Poging EE Addons DB automatisch te herstellen. in /home/deb73553n2/domains/nlsas.nl/public_html/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2263 What is a solution? |
|
I had the same problems with CREATE TABLE wp_esp_attendee_meta( |
|
It is strange, but we did find an issue with some of the recent changes to database scripts and have a ticket to ensure all database indexes are smaller than 191 characters. If you or anyone else would like to test the branch while it’s available for testing, it can be downloaded from here: |
|
The support post ‘Database failure [Index column size too large. The maximum column size is 767 by’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.