|
Jos
|
May 6, 2015 at 6:48 am
Multiple warning messages in Plugin page as follows:
Database table wp_esp_country existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? 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_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 wp_esp_country manually then restore to the backup again.
Now the weird thing is I never restored to a back up before I was alerted to these messages.
How I have tried to resolve this in order:
1) Upgraded to 4.6.25
2) Followed the instructions in the warning messages by adding the code to wp-config and tried restoring to a previous 2 different previous versions. messages still appear.
I did notice that when U upgrade to 4.6.25 it did not take do that extra step of adjusting the database data that it usually does.
What should I do next?
Thanks,
Joseph
|
|
Josh
|
May 6, 2015 at 7:01 am
Hi Joseph,
Can you let us know if prior to doing the update the database had been restored restored any backups, migrated servers, or there were modifications made to the database in anyway?
As a side note, if you updated from an older version of 4.6, then it shouldn’t run any migrations as it would have from 4.4 to 4.6.
|
|
Jos
|
May 6, 2015 at 7:56 am
Hi Josh,
Prior to updating to to 4.6.25 I did not restore to any old version. Only upgrades and they were released. No server migrations. No manual database changes. There may have been other plugin upgrades between 4.6.2 and 4.6.25. carried out through the Word Press plugin update core functionality.
Please also note that I did upgrade to 4.6.2 before WordPress upgrade to 4.2
So how may I resolve this?
|
|
Tony
|
May 6, 2015 at 11:01 am
Hi Jos,
Can you please go to Event Espresso -> Maintenance -> System Information.
Copy all of the information within the raw data section into a text file and email us that file please?
|
|
Tony
|
May 6, 2015 at 11:02 am
It would help if I added the email address to the post 🙂
Please send a copy to support[at]eventespresso.com
|
|
Jos
|
May 7, 2015 at 5:42 am
Hi Tony,
I did send the requested data to support[at]eventespresso.com. Haven;t heard back yet.
Thanks 🙂
|
|
Tony
|
May 7, 2015 at 6:37 am
Thank you.
Can you tell me at what point in the steps above did these messages appear?
You mention this:
Please also note that I did upgrade to 4.6.2 before WordPress upgrade to 4.2
So was the message shown before WP was updated or after?
Currently I suspect something within the WP securit update is confusing the code used to display those messages.
Your EE activation history shows you activated EE in this order :-
4.6.25.p
4.6.20.p
4.6.12.p
4.6.25.p
All on the 2015-05-06, which seems odd. Did you try multiple different versions (and previous versions) when this happened? (this is what I suspect is being cause by the WP update so just want to confirm)
|
|
Jos
|
May 7, 2015 at 9:28 am
Hi Tony,
I upgraded from 4.6.12.p to 4.6.20.p 2 weeks ago.
I had some styling errors you can read my ticket topic marked “styling errors after update”
Which I resolved by deleted all the file and uploading them again by FTP. I don;t recall reactivating the 4.6.12p at that time but I may have.
once I complete the upgrade to 4.6.20.p successfully by FTP I did not notice any errors at that time all seemed to be functioning properly.
The upgrade to WP 4.2 occurred after that. I still didn’t notice any errors.
On 2015-05-06 one of my site admins ( limited user roles) alerted me to the errors.
I decided to try update to the latest version first see if that solved them. I did so.
the errors didn’t disappear so I deactivated that version and reactivated each version as you have recorded above after insert the wp-config.php code recommended to resolve the issue in the error messages.
After unsuccessfully being able to resolve this on my own I then contacted support.
Kind regards,
Joseph
|
|
Tony
|
May 7, 2015 at 11:18 am
Thank you for breaking that down, it helps 🙂
The error messages are persistent messages, meaning once triggered, they will remain until they are dismissed. This is why changing the version numbers didn’t remove them.
A brief explanation of those error messages. Event Espresso checks if you have previously installed EE on your site and determines if you have the correct tables, need migrations etc.
What’s happening is EE checked for previous versions, didn’t find any but then checked the database for EE tables and DID find those. So it thinks those tables should not exist and that they will likely contain incorrect data.
Can you confirm your registration data is all still available? Check the transactions to.
Do you have a site backup from before 2015-05-06 (preferable before 2015-04-30) that we can install locally and try to reproduce?
|
|
Jos
|
May 7, 2015 at 11:33 pm
Hi Tony,
All Application data appears to be fully in order and intact.
Hmm ya I don’t think I have that back up of my site. My site is quite big with multiple online courses etc. and I don’t just run EE4 on it so I don’t think that is going to happen.
I can dismiss the message no problem I’d just like to know what can be done to to make EE4 think everything is ok. There is no issues with the application running except for this.
Regards,
Joseph
|
|
Tony
|
May 8, 2015 at 2:59 am
Hmm ya I don’t think I have that back up of my site. My site is quite big with multiple online courses etc. and I don’t just run EE4 on it so I don’t think that is going to happen.
That’s fine, I am running through various setups to try and reproduce this.
You can just simply dismiss all the messages.
You have activation history within your system information (which is what EE checks for for these messages), whilst there is activation history those errors should not be triggered again.
|
