Support

Home › Forums › Event Espresso Premium › Multiple warning of invalid table data (2)

Multiple warning of invalid table data (2)

Posted: September 6, 2015 at 4:20 pm

Viewing 19 reply threads


wmnf

September 6, 2015 at 4:20 pm

I did an upgrade from 4.7.9.p to 4.8.7.p a couple of days ago, but found multiple warnings only today after all checked out okay after the upgrade….

Database table wp_esp_event_question_group exists when it shouldn't, and may contain erroneous data. If you have previously restored your database from a backup that didn't remove the old tables, then we recommend adding
define( 'EE_DROP_BAD_TABLES', TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wp_esp_event_question_group. Afterwards you should undo that change from your wp-config.php file. 
If you cannot edit wp-config.php, you should remove the data from wp_esp_event_question_group manually then restore to the backup again.
Dismiss

There were many plugins updated at the same time including WordPress 4.2.4 to 4.3. All events, registrations and transactions are intact before and two since the upgrade, nothing seems amiss. I do find those tables in the database and have views using some of them, what should be done?


wmnf

September 6, 2015 at 4:21 pm

Oh, forgot to mention, I have not done any restores of the database at all. All updates completed without error and all appears fine with the site.


wmnf

September 6, 2015 at 5:02 pm

Just realized, one thing that did happen this morning, all updates to the CentOS 7 server were applied. Including an update to the mariadb package, which required a restart of MariaDB.


Tony

  • Support Staff

    •

September 8, 2015 at 6:45 am

Hi there,

I’ve asked one of our developers for some feedback on this.

However currently you can safely dismiss that message and continue using EE, it shouldn’t’ cause any further problems.


Brandon Gannon

September 8, 2015 at 11:06 am

I have the same problem.
Is the solution to just click DISMISS on all those warnings and ignore?


Brandon Gannon

September 8, 2015 at 11:20 am

Also: I did click on Dismiss for them but the website is running slow as molasses in January. Just got a 504 Gateway Time-Out.


Brandon Gannon

September 8, 2015 at 11:28 am

Here’s my full list of warnings. I can’t work on the site until this is fixed. It goes too slowly. Please help.

Database table feight_esp_event_question_group exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_event_question_group. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_event_question_group manually then restore to the backup again.

Dismiss

Database table feight_esp_event_venue exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_event_venue. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_event_venue manually then restore to the backup again.

Dismiss

Database table feight_esp_extra_meta exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_extra_meta. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_extra_meta manually then restore to the backup again.

Dismiss

Database table feight_esp_line_item exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_line_item. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_line_item manually then restore to the backup again.

Dismiss

Database table feight_esp_log exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_log. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_log manually then restore to the backup again.

Dismiss

Database table feight_esp_message_template exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_message_template. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_message_template manually then restore to the backup again.

Dismiss

Database table feight_esp_message_template_group exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_message_template_group. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_message_template_group manually then restore to the backup again.

Dismiss

Database table feight_esp_event_message_template exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_event_message_template. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_event_message_template manually then restore to the backup again.

Dismiss

Database table feight_esp_payment exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_payment. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_payment manually then restore to the backup again.

Dismiss

Database table feight_esp_payment_method exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_payment_method. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_payment_method manually then restore to the backup again.

Dismiss

Database table feight_esp_ticket_price exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_ticket_price. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_ticket_price manually then restore to the backup again.

Dismiss

Database table feight_esp_datetime_ticket exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_datetime_ticket. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_datetime_ticket manually then restore to the backup again.

Dismiss

Database table feight_esp_question exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_question. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_question manually then restore to the backup again.

Dismiss

Database table feight_esp_question_group_question exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_question_group_question. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_question_group_question manually then restore to the backup again.

Dismiss

Database table feight_esp_registration exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_registration. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_registration manually then restore to the backup again.

Dismiss

Database table feight_esp_registration_payment exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_registration_payment. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_registration_payment manually then restore to the backup again.

Dismiss

Database table feight_esp_transaction exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_transaction. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_transaction manually then restore to the backup again.

Dismiss

Database table feight_esp_venue_meta exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_venue_meta. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_venue_meta manually then restore to the backup again.

Dismiss

Database table feight_esp_price exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_price. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_price manually then restore to the backup again.

Dismiss

Database table feight_esp_price_type exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_price_type. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_price_type manually then restore to the backup again.

Dismiss

Database table feight_esp_ticket exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_ticket. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_ticket manually then restore to the backup again.

Dismiss

Database table feight_esp_question_group exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding

define( ‘EE_DROP_BAD_TABLES’, TRUE );

to your wp-config.php file then restore to that backup again. This will clear out the invalid data from feight_esp_question_group. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from feight_esp_question_group manually then restore to the backup again.


Josh

  • Support Staff

    •

September 8, 2015 at 11:40 am

Hi there,

The message has specific instructions to add define( 'EE_DROP_BAD_TABLES', TRUE ); to your wp-config.php file, then remove, then restore to your previous backup. Is that something you can do?


Brandon Gannon

September 8, 2015 at 12:14 pm

Yes, can do. I was just hoping it wouldn’t come to that.
What’s going on here? Did something get corrupted?
We did not restore from backup, just updated EE.


Brandon Gannon

September 8, 2015 at 12:42 pm

OK, I did as instructed:

Added the line to wp-config.php
define( ‘EE_DROP_BAD_TABLES’, TRUE );
Uploaded that to server.

Then restored to yesterday’s database.

Same problem. Still getting the vast list of error warnings.
And site running really slow.


Josh

  • Support Staff

    •

September 8, 2015 at 12:57 pm

Those errors can also happen if someone (or some plugin) was playing with the espresso_db_update wp option. Can you send a copy of the system status page to support at eventespresso.com so we can investigate further?


Brandon Gannon

September 8, 2015 at 1:14 pm

I’ve sent the system info.
And maybe the problem is gone. Once I did as instructed, the error warnings were still there.
BUT: once I clicked DISMISS on all of them, they stayed gone. Previously (before a restored from backup) the warnings had re-appeared on every pageload, even after I clicked Dismiss.
Not sure about site speed being back to normal.
Weird.


Brandon Gannon

September 8, 2015 at 2:38 pm

Still NOT fixed. Now we’re getting this error:

Could not create instance of class Country from row Country.CNT_active=0&Country.CNT_ISO=&Country.CNT_ISO3=&Country.RGN_ID=0&Country.CNT_name=&Country.CNT_cur_code=&Country.CNT_cur_single=&Country.CNT_cur_plural=&Country.CNT_cur_sign=&Country.CNT_cur_sign_b4=0&Country.CNT_cur_dec_plc=0&Country.CNT_cur_dec_mrk=&Country.CNT_cur_thsnds=&Country.CNT_tel_code=&Country.CNT_is_EU=0 EEM_Base – _create_objects – 3499


Josh

  • Support Staff

    •

September 9, 2015 at 7:15 am

Hi Brandon,

At any point before the warnings showed up had anything been done to “clean up” the wp_options table? The system status report indicates that at the very least, your espresso_db_update wp option somehow got deleted. W could tell because the “activation history” shows you only installed 4.8.7.p, but your migration history shows you have had EE active at least since 4.4 because they ran the 4.5 migration.
So can you think of a possible way how your “espresso_db_update” wp option got deleted? Might the entire table been deleted? Is there a plugin that’s set up to clean up options from the wp_options table?


Brandon Gannon

September 9, 2015 at 7:34 am

Not that I know of.
And update: after a couple tries restoring from backup, we asked the host (mediatemple) to step us backward 48 hours. Still same problem.
We’re dead in the water. What to do?


Josh

  • Support Staff

    •

September 9, 2015 at 9:13 am

Can you check with your host to see if you can get a backup where the data in the wp_options table is intact?


Brandon Gannon

September 9, 2015 at 9:28 am

I have database backups back to August 1. When I search any of them for “espresso_db_update” I get nothing.


Josh

  • Support Staff

    •

September 9, 2015 at 10:43 am

Can you look in your database and see if there is currently a valid value for espresso_db_update in your wp_options table? If not, you can try adding a new row in the options table, name it espresso_db_update, and set its value to:

a:2:{s:7:"4.8.4.p";a:1:{i:0;s:19:"2015-09-09 16:39:10";}s:7:"4.8.7.p";a:1:{i:0;s:19:"2015-09-09 16:40:23";}}

Then save. If the warnings come back again, you can check to see if the espresso_db_update option has been deleted again. If it’s been deleted then the next step is find what’s deleting it.


Brandon Gannon

September 10, 2015 at 9:03 am

OK, sorry for the delay. We had some communication problems.
I was wrong on one count: the host had not yet restored the database from backup. They have now done so and we’re back in business.
Yes espresso_db_update is in the database and its value is:
(2624,’espresso_db_update’,’a:20:{s:10:\”3.1.36.5.L\”;a:1:{i:0;s:12:\”unknown-date\”;}s:11:\”4.4.4.decaf\”;a:1:{i:0;s:19:\”2015-02-05 15:12:34\”;}s:8:\”4.6.11.p\”;a:1:{i:0;s:19:\”2015-02-26 20:09:28\”;}s:8:\”4.6.13.p\”;a:1:{i:0;s:19:\”2015-03-04 18:39:26\”;}s:8:\”4.6.14.p\”;a:1:{i:0;s:19:\”2015-03-06 01:32:45\”;}s:8:\”4.6.18.p\”;a:1:{i:0;s:19:\”2015-04-06 17:36:09\”;}s:8:\”4.6.19.p\”;a:1:{i:0;s:19:\”2015-04-09 17:16:01\”;}s:8:\”4.6.20.p\”;a:1:{i:0;s:19:\”2015-04-18 18:06:15\”;}s:8:\”4.6.22.p\”;a:1:{i:0;s:19:\”2015-04-22 21:33:13\”;}s:8:\”4.6.23.p\”;a:1:{i:0;s:19:\”2015-04-23 22:29:52\”;}s:8:\”4.6.25.p\”;a:1:{i:0;s:19:\”2015-05-04 22:31:09\”;}s:8:\”4.6.26.p\”;a:1:{i:0;s:19:\”2015-05-13 22:35:07\”;}s:8:\”4.6.28.p\”;a:1:{i:0;s:19:\”2015-05-20 23:41:38\”;}s:7:\”4.7.1.p\”;a:1:{i:0;s:19:\”2015-06-17 00:16:17\”;}s:7:\”4.7.9.p\”;a:1:{i:0;s:19:\”2015-07-24 13:37:08\”;}s:8:\”4.7.10.p\”;a:1:{i:0;s:19:\”2015-08-17 23:24:20\”;}s:7:\”4.8.2.p\”;a:1:{i:0;s:19:\”2015-08-18 23:58:33\”;}s:7:\”4.8.4.p\”;a:1:{i:0;s:19:\”2015-08-20 16:52:14\”;}s:7:\”4.8.7.p\”;a:1:{i:0;s:19:\”2015-08-31 18:54:42\”;}s:7:\”4.8.8.p\”;a:1:{i:0;s:19:\”2015-09-10 00:08:54\”;}}’,’no’)

Make sense?
So we’re back to where we were, no error messages. Breathing a sigh of relief.
We did learn through this that the db backup plugin we were using was crap. We are glad MediaTemple had a good backup, worth the charge to restore.


Josh

  • Support Staff

    •

September 10, 2015 at 9:06 am

Thanks for the follow up, and I’m glad to hear your site is back up and running.
Viewing 19 reply threads

The support post ‘Multiple warning of invalid table data (2)’ 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 Josh 9 years, 2 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso