Support

Home Forums Event Espresso Premium EE directory error

EE directory error

Posted: October 12, 2017 at 10:36 am

Viewing 2 reply threads


clrc

October 12, 2017 at 10:36 am

I received the following directory error message after attempting to update to 4.9.47.p. It says at the end that all updates have been completed, however EE is not working or displaying on our site. Any help is much appreciated as we are currently accepting event registrations through EE.

The update process is starting. This process may take a while on some hosts, so please be patient.

Enabling Maintenance mode…

Updating Plugin Event Espresso (1/1)

Downloading update from …
Unpacking the update…

An error occurred while updating Event Espresso: Could not create directory.
Disabling Maintenance mode…

All updates have been completed.


clrc

October 12, 2017 at 10:56 am

I tried deactivating EE with the intent to reactive it and see if things worked, however I then received the following:

The following errors have occurred:
There were errors creating the Event Espresso database tables and Event Espresso has been deactivated. To view the errors, please enable WP_DEBUG in your wp-config.php file.

WordPress database error: [Table ‘clrc_esp_event_question_mailchimp_field’ already exists]
CREATE TABLE clrc_esp_event_question_mailchimp_field ( QMC_ID INT UNSIGNED NOT NULL AUTO_INCREMENT , EVT_ID INT UNSIGNED NOT NULL , QST_ID TEXT NOT NULL , QMC_mailchimp_field_id TEXT NOT NULL , PRIMARY KEY (QMC_ID) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

Stack Trace:#0 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(688): EventEspresso\core\services\database\TableManager->createTable(‘esp_event_quest…’, ‘ QMC_ID INT UNS…’, ‘InnoDB’) #1 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(557): EEH_Activation::create_table(‘esp_event_quest…’, ‘ QMC_ID INT UNS…’, ‘ENGINE=InnoDB’, false) #2 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(490): EE_Data_Migration_Script_Base->_create_table_and_catch_errors(‘esp_event_quest…’, ‘ QMC_ID INT UNS…’, ‘ENGINE=InnoDB’, false) #3 /var/www/html/clrc.org/wp-content/plugins/eea-mailchimp/db/migration_scripts/EE_DMS_MailChimp_2_3_0.dms.php(80): EE_Data_Migration_Script_Base->_table_should_exist_previously(‘esp_event_quest…’, ‘ QMC_ID INT UNS…’, ‘ENGINE=InnoDB’) #4 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/EE_Addon.core.php(356): EE_DMS_MailChimp_2_3_0->schema_changes_before_migration() #5 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/EE_Addon.core.php(313): EE_Addon->initialize_db() #6 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(539): EE_Addon->initialize_db_if_no_migrations_required() #7 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2446): EE_System->initialize_addons() #8 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2380): EEM_Base->_verify_addons_db(‘get_results’, Array) #9 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2391): EEM_Base->_process_wpdb_query(‘get_results’, Array) #10 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2322): EEM_Base->_process_wpdb_query(‘get_results’, Array) #11 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(1063): EEM_Base->_do_wpdb_query(‘get_results’, Array) #12 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(942): EEM_Base->_get_all_wpdb_results(Array, ‘ARRAY_A’, NULL) #13 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/admin_pages/events/Events_Admin_Page.core.php(1885): EEM_Base->get_all(Array) #14 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/admin_pages/events/Events_Admin_List_Table.class.php(33): Events_Admin_Page->get_events(10, 1) #15 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_List_Table.core.php(214): Events_Admin_List_Table->_setup_data() #16 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(1736): EE_Admin_List_Table->__construct(Object(Extend_Events_Admin_Page)) #17 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(1690): EE_Admin_Page->_set_list_table_object() #18 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page.core.php(607): EE_Admin_Page->_set_list_table() #19 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php(322): EE_Admin_Page->_load_page_dependencies() #20 /var/www/html/clrc.org/wp-content/plugins/event-espresso-core-reg/core/admin/EE_Admin_Page_CPT.core.php(304): EE_Admin_Page_CPT->_load_page_dependencies() #21 [internal function]: EE_Admin_Page_CPT->load_page_dependencies(”) #22 /var/www/html/clrc.org/wp-includes/class-wp-hook.php(298): call_user_func_array(Array, Array) #23 /var/www/html/clrc.org/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(”, Array) #24 /var/www/html/clrc.org/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #25 /var/www/html/clrc.org/wp-admin/admin.php(212): do_action(‘load-toplevel_p…’) #26 {main}


Josh

  • Support Staff

October 12, 2017 at 1:06 pm

Hi Ryan,

It sounds like some of the options from your wp_options table got wiped out somewhere along the way. Event Espresso will check the options table for a “db table is already created option” before it goes and tries to create tables.

If you have Event Espresso activated right now, can you go to

yoursite.com/wp-admin/admin.php?page=espresso_maintenance_settings&action=data_reset

If that page loads then you click on the Reset Event Espresso Capabilities button. That will restore the capabilities that got wiped from the database by some earlier action.

Viewing 2 reply threads

The support post ‘EE directory error’ 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.

Event Espresso