Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Registration Data Stored Wrong - Please Read | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Registration Data Stored Wrong – Please Read

Registration Data Stored Wrong – Please Read

Posted: November 30, 2012 at 12:38 pm

Viewing 2 reply threads


nmcmullin

November 30, 2012 at 12:38 pm

I am having a bit of an emergency here. I implemented the plugin for a company, they took about 25-30 registrations so far, seemed to work fine, they checked an Excel Export and saw that the registration details were unique but some questions all had the same answer and address/personal info. Also this is the case when viewing the attendees via the WP backend – the main list shows unique names, but when opening that attendee record it has someone else’s address/firstname/questions&answers. Now, when I generate a PDF invoice for this user, the correct information is shown in the PDF record. So this is alarming as many of these users paid via PayPal and while their transaction is unique I need to get their data correctly … I am running the latest version of WordPress and Event Espresso. Thank you!!!


nmcmullin

November 30, 2012 at 12:41 pm

So I noticed that .4 fixed a but with data stored wrong, I updated to the latest build (3.1.28.5.P ), but the data still shows wrong, even though it might be entered “new” Ok, how can I fix the records that have been entered incorrectly? But still must have the correct data as the PDF Invoice shows as such …

3.1.28.4

Hotfix
These fixes were made in 3.1.28.2 but were rolled back somehow in 3.1.28.3 (see this thread)
single attendee overview name and email fields getting autofilled with another attendees data
export data displays the same name for all attendees


Josh

November 30, 2012 at 6:08 pm

Hi there,

I’m sorry for the trouble. We pushed a fix out and sent an email out to everyone that had downloaded 28.3 about the critical hotfix update. Seth wrote more about what happened here:
http://staging.eventespresso.com/topic/important-update-3-1-28-4/

I saw that Jonathan followed up with you in an email with instructions on how to restore the data from a backup. I hope that will help.

I’ll explain a bit more about what was affected. It’s the data in the events_answer table that was affected, which stores the answers to the custom questions. The primary attendee info is all stored in the events_attendee table, and was not affected by the bugs in 28.1 and 28.3.
Viewing 2 reply threads

The support post ‘Registration Data Stored Wrong – Please Read’ 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.

The original Forum description...

Status: closed

Updated by Josh 12 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server