Home Forums Event Espresso Premium Confirmation process changed

Confirmation process changed

Posted: September 7, 2012 at 6:18 am


September 7, 2012 at 6:18 am

We have used EE version 3.1.15P and now upgrading to 3.1.26. Sorry to inform that the booking process have changed between these versions.
The old version put the attendee with event_id=0 and not visible to the administrator until the visitor had confirmed the booking. In this version the visitor is confirmed and add to the event when looking at his booking (and not confirmed).
Why is this step changed?

Chris Reynolds

  • Support Staff

November 3, 2012 at 10:33 am

Sorry for not finding this sooner. I’m just going through old forum threads today…

The process hasn’t (or shouldn’t have) changed. The process has always been that attendees are created at the time they submit their information. That information is stored in the database. If they complete the registration process, then they show up as completed transactions and take up one of the available spaces. If they do not complete payment, their registration is left as Incomplete and they do not take up one of the available spaces. The only time this is different is if you have changed the default attendee status to Pending in which case attendees are in Pending status (which takes up an available space) until they complete payment.

In any of these cases the attendees would be viewable by the admin unless the list attendees page is being filtered to only display attendees who have completed the registration process.

The support post ‘Confirmation process changed’ 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.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Chris Reynolds 7 years, 5 months ago ago

Topic Tags


This topic is: not resolved
Do NOT follow this link or you will be banned from the site!