Support

Home Forums Event Espresso Premium Plugin stopped working after server crash with host company

Plugin stopped working after server crash with host company

Posted: May 12, 2018 at 5:10 am


paulgreen

May 12, 2018 at 5:10 am

Hello – I hope you can help as this is quite urgent as I run my networking event business using your plugin and after my website went down due to problems with the host for 4 hours, on recovery, the Espresso plugin is not functioning.

The dashboard comes up with the following error:

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 ‘wp_esp_people_to_post’ already exists]
CREATE TABLE wp_esp_people_to_post ( PTP_ID bigint(20) unsigned NOT NULL AUTO_INCREMENT, PER_ID bigint(20) unsigned NOT NULL DEFAULT 0, OBJ_ID bigint(20) unsigned NOT NULL DEFAULT 0, OBJ_type varchar(50) NOT NULL DEFAULT ‘Event’, P2P_Order tinyint(3) NOT NULL DEFAULT 0, PT_ID bigint(20) unsigned NOT NULL DEFAULT 0, PRIMARY KEY (PTP_ID), KEY PER_ID (PER_ID), KEY OBJ_ID (OBJ_ID), KEY OBJ_type (OBJ_type), KEY PT_ID (PT_ID) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

redacted

A database error has occurred. Turn on WP_DEBUG for more information.

And this comes up when I try and access any of the Espresso menu:

The incoming statuses argument must be an array with keys as the $status_id and values as the $status_code EEM_Status – localized_status – 284

Help!

Thanks, Paul.

  • This topic was modified 4 months, 2 weeks ago by  Josh. Reason: removed stacktrace that included server paths


Tony

  • Support Staff

May 14, 2018 at 3:21 am

Hi Paul,

The first error:

WordPress database error: [Table ‘wp_esp_people_to_post’ already exists]

means EE is trying to create a table that already exists (for the people add-on), the strange part is EE checks for the table before attempting to create it so it should not throw that error if it has access to the tables in the DB.

The second error:

The incoming statuses argument must be an array with keys as the $status_id and values as the $status_code EEM_Status – localized_status – 284

Usually means your site doesn’t have the correct privileges to create new tables in your database, or update specific tables already created in the database.

May I ask what the problem with the host was and what was done to fix it? It’s likely related to the errors you are getting now.


paulgreen

May 14, 2018 at 3:59 am

Thanks for your prompt reply – I have passed on to the host providers. I raised a ticket with them last Friday after my site was down for 4 hours and when it came back up, EE wasn’t working; nor was a sub-domain which hosts a CRM system for my business. Unfortunately, they have not been that responsive given that my networking business runs on EE. I still don’t know what exactly caused the website to go down.


paulgreen

May 14, 2018 at 6:08 am

Just to let you know, the host has now installed a back up of the database and the EE plug-in is working fine. Thanks for your support.

The support post ‘Plugin stopped working after server crash with host company’ 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.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  paulgreen 4 months, 2 weeks ago ago

Topic Tags

Notifications

This topic is:
pending
Do NOT follow this link or you will be banned from the site!