|
3k-user
|
September 7, 2016 at 11:34 pm
After one of the last EE4 updates all attendee, transaction and ticket information is gone. The complete attendee table within the database has been cleaned. All events are still present and visual adjustments to the order process are still active.
1. Can this happen because of an “automatic” update? Or could the only explanation be that a site user/manager made a mistake?
2. Is there a way to reverse or restore this process?
Thank you in advance for all information and help.
|
|
Tony
|
September 8, 2016 at 2:36 am
Hi there,
The complete attendee table within the database has been cleaned.
So when you view the table(s) within phpmyadmin or similar they completely empty?
If so which tables?
1. Can this happen because of an “automatic” update? Or could the only explanation be that a site user/manager made a mistake?
We don’t have enough information to go on, however we don’t have any code that would automatically wipe your database within EE. There is a feature to ‘reset’ the tables back to default however it would wipe everything and is only ran when manually requested within Event Espresso -> Maintenance -> Reset/Delete Data or when a you chose not to migrate your event data when running migrations.
What was the last version of EE you updated from? If you go to Event Espresso -> Maintenance -> System Information you’ll find a ‘ee_activation_history’ section.
At the bottom of that section you’ll see the latest update version your ran. Do you have any jumps in the version numbers there? As in updates from 4.6 or 4.7 -> 4.9.
2. Is there a way to reverse or restore this process?
If the details have been removed from the database you will need to restore to a backup that contained the details. The database is the only place all the details are saved, if they are removed there is no way to restore them without a backup.
|
|
3k-user
|
September 14, 2016 at 11:27 am
Hi Tony,
So when you view the table(s) within phpmyadmin or similar they completely empty?
The following tables where completely empty:
Between the time the “reset” or “error” happened and the time I discovered it a few records of standard “free” tickets that wheren’t available before had been added. Mainly from people that saw the system wasn’t functioning anymore that wanted to test how much of the process had changed from the way it was.
- esp_attendee_meta
- esp_answer
- esp_attendee_meta
Components that have also been reset:
- Questions and question-groups
- Transactions
The “esp_transaction” table contains empty transactions “TXN_total” contains 0.000 in every transaction I guess since the moment the error happened and those records do not show up in the admin trransactions page.
What was the last version of EE you updated from?
The “ee_activation_history” section shows:
4.9.1.p 2016-09-03 00:01:03
This cannot be true because we started with a EE 3 version and updated to the 4 version when te system told us that a major update was available. At that time all data was still available. There should be at least 4 ee_activation_history records of version updates.
It almost looks like someone reinstalled the plugin.
Unfortunately I didn’t create a daily backup. I can restore the data of two months ago but then I would still need to reimport the tickets sold since then.
I’ve got all the emails sent when a ticket is sold in a mailbox so I can create a .csv with the First name, Last name, Number of tickets and the Ticket barcode. I can see that there is a .csv import in EE3. Is it at all possible to do the same in EE4? (Even with SQL)
|
|
Josh
|
September 14, 2016 at 11:36 am
There isn’t a csv import for EE4, but what you could do is check with the host, they may be taking daily backups that you can restore to.
|
|
3k-user
|
September 17, 2016 at 8:16 am
Josh and Tony,
Thank you for all the information and feedback. I was lucky enough a VPS backup was created daily. That helped me to restore almost all lost information.
For now I will close the ticket. If I have more questions I will look into reopening this ticket or creating a new one if the topic differs a lot from this one.
|
