Support

October 18, 2012 at 10:11 am

Hi there,

This is happening because the database structure has changed between 3.0.19 to what’s available now. What I can recommend is reverting back to the older version, exporting out all the attendee data, removing this data, then updating.

After updating to the newer version of Event Espresso, any new registrations going forward will automatically be set to ‘incomplete’ unless the default payment status option is changed. If you’re using one of the offline payment methods, such as the invoice options, when the registrant downloads the invoice it will set the status to pending. If you’re using one of the online payment options, the payment status will be set to complete when the payment notification comes back from the payment processor.

October 22, 2012 at 11:16 am

The database structure changes when you update from 3.0.x to 3.1.x. Back about over a year ago when the 3.1.x branch was the stable branch and people were updated from 3.0.x we advised them to let the open events finish registration before updating, because the attendee records from the 3.0.x branch would not be compatible with 3.1.x.

If your client needs to access the attendee data from events that were registered under 3.0x, you could set up a clone of the existing site for accessing the older events, then set up the live site to use the current version for all events going forward.