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
Attendee data missing after update from 3.0.14. | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Attendee data missing after update from 3.0.14.

Attendee data missing after update from 3.0.14.

Posted: March 18, 2013 at 3:20 pm

Viewing 5 reply threads


Laura Carniel

March 18, 2013 at 3:20 pm

Hi,

We updated Event Espresso today from 3.0.14 The attendee address fields are now all blank. We did add one new field to the registration from before the address. Did that wipe out the rest of the fields? How can we restore this?


Jonathan Wilson

  • Support Staff

    •

March 18, 2013 at 3:33 pm

Hi Laura,

There are two things to check/do before upgrading from 3.0.19.x. Did you do these? Do you have a backup?

  1. Back up your database. There are a lot of plugins that can do this. Having a backup of the database means you can go back to the way your site was before if something goes awry.

  2. Make sure you do not have any currently active events. The issues we have had reported from earlier versions of Event Espresso have all been surrounding attendee data and payment information. We have not been able to reproduce the problems on our test servers, but we are handling and calling some data differently in the newer versions of the plugin, so the problems that were reported were around those areas.


Laura Carniel

March 18, 2013 at 3:42 pm

I do have a complete backup with backup buddy. Yes we had active events but I deactivated the plugin so events would all be deactivated no?

Is there a way to restore the addresses from the database?


Jonathan Wilson

  • Support Staff

    •

March 18, 2013 at 4:00 pm

Great. You will probably need to restore via backup buddy. Are you events recurring? What is the end date on the events?


Ruth

March 19, 2013 at 11:57 am

Well if I do a backup buddy restore it will take the site back to the old plugin version and I’ll have to start the whole update process over. If I do that what do I have to do to keep the attendee addresses? AND there have been some signups since moving to the new version… those would be lost. I see the addresses in the WordPress database – is there a way to pull them back in? run a query or something?

We currently have events open till June 9th.


Chris Reynolds

  • Support Staff

    •

March 20, 2013 at 11:51 am

Ruth, it may be possible, we had one of our developers looking at it yesterday. Can you fill out the form here with as much information as possible so we can take a look?

http://evts.io/logininfo
Viewing 5 reply threads

The support post ‘Attendee data missing after update from 3.0.14.’ 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 Chris Reynolds 11 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server