|
Suhaib Siddiqi
|
September 5, 2016 at 8:03 pm
Everything was working. I had been using EE4.x since almost a year. All of sudden today I started getting hundreds or errors like following one, for every EE table. I did not do changes to database.
Database table bdc_esp_country 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 bdc_esp_country. 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 bdc_esp_country manually then restore to the backup again.
|
|
Suhaib Siddiqi
|
September 5, 2016 at 8:03 pm
Everything was working. I had been using EE4.x since almost a year. All of sudden today I started getting hundreds or errors like following one, for every EE table. I did not do changes to database.
Database table bdc_esp_country 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 bdc_esp_country. 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 bdc_esp_country manually then restore to the backup again.
|
|
Tony
|
September 6, 2016 at 3:52 am
Hi there,
All of sudden today I started getting hundreds or errors like following one, for every EE table.
Do you actually see hundreds of notices or about 30-40?
Hundred’s means there is a loop that shouldn’t be happening at all.
30-40 means you’re seeing that notice for each EE table in the database.
Have you modified the database at all? Restored from a backup etc?
|
|
Suhaib Siddiqi
|
September 6, 2016 at 6:50 am
30-40 messages. i.e. one message for each table. I did not modify the database or restored from backup. The messages started appearing since yesterday.
|
|
Tony
|
September 6, 2016 at 7:01 am
They are persistent notices and will remain until you dismiss them from the Dashboard. To dismiss the notices you will need to click the link in the bottom right of each of the notices.
If you have not modified the database at all and not restored any backups then its sounds like a false positive, especially as they are showing for all tables.
If you go to Event Espresso -> Maintenance -> System Information.
Look for the ‘ee_activation_history’ section, does it show a full history of your EE versions or just the most recent?
|
|
Suhaib Siddiqi
|
September 6, 2016 at 8:16 am
It shows only current version. It shows under ee_activation history,
4.9.9.p
2016-09-06 01:18:08
2016-09-06 01:53:30
Undr migration history, it shows 4.1.0 to 4.9.0.
|
|
Tony
|
September 6, 2016 at 10:14 am
So somehow your EE activation has been removed so the notices you’ve seen are ‘expected’, but not (I know, right!)
EE checks for any EE tables within your database and then compares those tables to what ‘should’ be there. For example if you activate a version of EE that should NOT have the esp_log table for example, EE checks the DB, find the table, checks the activation history and see’s that table should not exist… then throws that notice.
In your case your activation history has been removed, so then EE found all these esp_ tables that as far as your history is concerned, should not be there and threw the notices. You can safely dismiss those notices and as long as your activation history is not wiped again they should not appear again.
Do you run any security/cleanup/optimization plugins on this site?
|
|
Suhaib Siddiqi
|
September 6, 2016 at 10:32 am
Yes, I do run Autoptimize plugin to clean up tables once a month. That plugin had been in use since long time. I am not sure why all of a sudden these messages will appear.
I have dismissed the messages.
|
|
Tony
|
September 7, 2016 at 2:30 am
We have an open ticket to investigate and I will add this thread to that ticket.
We have had a couple of users report this but we’ve been unable to track down the cause and have been unable to reproduce the problem locally so we suspect another plugin is ‘cleaning’ the DB and removing the field.
However as mentioned now that you have removed the notices EE should continue to work as expected.
|
