|
scboston
|
November 8, 2012 at 12:05 pm
When attempting to export an Excel file of all the attendees for a particular event, the .xls file comes out with all the payment information correct, yet with the name and contact information of each person incorrectly duplicated as the exact same name and contact info for every single entry (throughout all events and everywhere). This is also occurring when just viewing a particular attendee’s specific information from within the site. I’ve deactivated and reactivated the Event Espresso plugin, but with no change. This has all occurred since updating to the latest version yesterday. With events occurring this weekend and no individual registration information, this is a massive problem for us. Any help asap would be much appreciated.
|
|
Dean
|
November 9, 2012 at 1:54 am
Hi,
We did a hotfix on this, please install 3.1.28.2.P
https://eventespresso.com/topic/urgent-please-stand-by-for-an-important-bug-fix-release/
Apologies for any inconvenience.
|
|
scboston
|
November 9, 2012 at 6:49 am
I’ve updated to that and still no improvement. All my records are incorrect and I’m completely lost as to how to recover them. I don’t believe we have a backup, nor am quite sure about how to recover one from Bluehost. I’ve sent my login info to you via the online contact form. Could you please assist me further?
|
|
Josh
|
November 9, 2012 at 7:05 am
Hi there,
Sorry for the trouble. I checked and did not see the log in info in our support inbox. Can you try to resend?
We’ve isolated the issue down to the events_answers table. The events_attendee table will be intact, and can be exported into an excel spreadsheet so you’ll have a hard copy of the general attendee records. This can be done via phpmyadmin via the host control panel or by installing adminer. Please let us know if you’d like assistance with that.
Here’s a link to Bluehost’s documentation on how to retrieve a snapshot of the database:
https://my.bluehost.com/cgi/help/4
|
|
Chris Reynolds
|
November 13, 2012 at 11:25 am
This issue has been resolved in 3.1.28.3, though anyone who is seeing this issue from before the update may need to restore their database to an earlier version. Closing this to new replies since it’s resolved in the latest hotfix.
|
