Support

Home Forums Event Espresso Premium EE4 Events page to show not only Approved registrations

EE4 Events page to show not only Approved registrations

Posted: April 30, 2015 at 9:52 am


Jonathan

April 30, 2015 at 9:52 am

I would like the overview table to show not only approved registrations but also pending payment and incomplete (and perhaps others).

How would I add this information?

Thanks


Tony

  • Support Staff

April 30, 2015 at 12:16 pm

Hi Jonathan,

Can you tell me which registration list you are viewing please?

Event Espresso should include Approved and Pending Payment registrations by default.

Incomplete registrations are registrations with no contact information, so there is no point in displaying them at that point. They will only clutter the list with registrations that you can not use which is why they are within their own filter.


Jonathan

April 30, 2015 at 12:31 pm

It’s the page you get when you click “Events Espresso” – “Events”.

The table contains the following column headings:

ID	Name	Venue	Event Start	On Sale	** Actions

Where the ** is is the green “people” picture for number of Approved Registrations.

When you click on the blue “people” icon for “View Registrations”, various types of registration are displayed (approved, pending payment, incomplete etc).

Incidentally, I guess “incomplete” is different to “Abandoned”? (Which is the word you get when you hover over the orange shopping basket.) Is that right?

What I’d like the “Events Espresso – Events” page to have is extra columns at ** for at least the Pending-Payment and Abandoned registrations (and maybe a total).


Tony

  • Support Staff

May 1, 2015 at 6:33 am

Thank you, I understand now.

When you click on the blue “people” icon for “View Registrations”, various types of registration are displayed (approved, pending payment, incomplete etc).

When you click to view the registrations using that button, you are shown Approved and Pending Payment registrations. The incomplete registrations should only be shown within their own filter.

There are different stauts types that use the same color, for example….

Incomplete registrations use an orange REG Strip color.

Abandoned transactions use orange on the transaction date.

They are not the same and apply differently, which leads onto…

Incidentally, I guess “incomplete” is different to “Abandoned”? (Which is the word you get when you hover over the orange shopping basket.) Is that right?

There are Incomplete registrations and Incomplete transactions.

Incomplete registrations are registrations that have no contact information, they look like this – http://take.ms/Mc0Cv

Notice I am viewing registrations there, clicked on the Incomplete filter. Those registrations have failed transactions (the red TXN date underlined)

Incomplete transactions are transactions that owe monies, you can have an Approved/Pending Payment (or other) registration within an incomplete transaction status, for example – http://take.ms/4cD6q

Finally Abandoned transactions (again can be on multiple types of registrations) usually happen when the user has clicked to go to an offsite payent method such as PayPal standard, then never returned to the site… either they closed the browser, or paid then didn’t return to the site afterwards. They never Finalized the registration, and so the transaction shows Abandoned (if they did pay via PayPal this will update when the session expires later)

Does that help?


Jonathan

May 1, 2015 at 10:12 am

First of all, can I try to restate my question? My confusion about terminology made my original intention unclear.

In the Events Overview page there is only one number for each course – it is the number of Approved Registrations. I would like the table also to display the number of Pending-Payment Registrations per course (I only accept Stripe/Paypal so these will likely all relate to Abandonded Transactions).

Secondly, can I try to summarise in my own words your useful information, to check I understand?

In relation to Transactions:

– The difference between Incomplete Transactions and Abandoned Transactions is that with Abandoned transactions the user has not finalised the registration (e.g. he proceeded to payment options – but did not make a selection / selected Stripe but did not “Pay no” / selected Paypal but did not return).

– If the user does not return from Paypal, but HAD paid in full, the registration will in due course be finalised automatically, which would change the transaction to to Complete (and the registration, with my settings, to Approved).

– Incompete Transactions occur where (e.g.) payment later on is permitted and registration has been finalised despite payment not yet having been made. If, as on my site, payment is required immediately by Paypal/Stripe then it wouldn’t be possible to finalise the registration, so it would be an Abandoned Transaction instead.

And finally, can I ask some more questions?

1. How do Incomplete Registrations (with no contact information) come into existence? Even with a Failed Transaction you’d think the user information would still be saved.

2. Are Failed Transactions where users have tried to pay but (e.g.) Paypal or Stripe has not let them?

Thank you very much


Tony

  • Support Staff

May 1, 2015 at 12:33 pm

In the Events Overview page there is only one number for each course – it is the number of Approved Registrations. I would like the table also to display the number of Pending-Payment Registrations per course (I only accept Stripe/Paypal so these will likely all relate to Abandonded Transactions).

I understand what you mean, currently this isn’t available. However, with the information below this may no be needed….

In relation to Transactions:
– The difference between Incomplete Transactions and Abandoned Transactions is that with Abandoned transactions the user has not finalised the registration (e.g. he proceeded to payment options – but did not make a selection / selected Stripe but did not “Pay no” / selected Paypal but did not return).

Stripe is an onsite payment method so should not create Abandoned transactions, only Incomplete, but yes that’s correct. Selecting PayPal and either not paying, or not returning to the site after paying, will leave the Transaction status as abandoned.

– If the user does not return from Paypal, but HAD paid in full, the registration will in due course be finalised automatically, which would change the transaction to to Complete (and the registration, with my settings, to Approved).

Correct. Note what happens is EE sets up a cron to basically re-evaluate the Transaction when the sessions expires (default is 2 hours).

– Incompete Transactions occur where (e.g.) payment later on is permitted and registration has been finalised despite payment not yet having been made. If, as on my site, payment is required immediately by Paypal/Stripe then it wouldn’t be possible to finalise the registration, so it would be an Abandoned Transaction instead.

Just to throw a spanner in the works…. Yes… and No. Your description of an Incomplete transaction is correct, however, Abandoned transactions from PayPal, will switch to ‘Incomplete’ when the cron from above re-evaluates the transaction. No payment made? Switch to Incomplete. (I didn’t include this above so based on my previous statement that would be correct)

1. How do Incomplete Registrations (with no contact information) come into existence? Even with a Failed Transaction you’d think the user information would still be saved.

2. Are Failed Transactions where users have tried to pay but (e.g.) Paypal or Stripe has not let them?

I’m going to answer these together as they are linked. First #2, No they are not failed payments (again payments have their own status within a transaction)

We need to store the information ‘somewhere’ within EE, I won’t go into details but recently we had to change how we did this and basically we store registrations ‘as soon as they are created’…

So when you select a ticket and click register (you haven’t entered any details yet) a Incomplete Registration is created for that registrations. Registrations need an associated transaction, so a ‘Failed’ transaction is created.

As you input your attendee details the registration is updated to Pending Payment, the transaction Incomplete. Then depending on what payment method you use, the Transaction updates, as will the Registration.

That all make sense?

I’d like to point out that knowing the above, you can see that numbers of ‘Incomplete’ registrations and ‘Failed’ transactions do not indicate a problem. If you are still taking normal registration (that have the status mentioned above), but also have those, it is expected behaviour and is likely everything is working as expected.


Jonathan

May 1, 2015 at 2:07 pm

Thank you very much for taking the trouble to explain this. I will re-read it to get my head round it fully! For future releases, it would be great to have the option of also showing the number of “pending payment” registrations on the “events overview” page (perhaps with a caveat about taking it with a pinch of salt).

The support post ‘EE4 Events page to show not only Approved registrations’ 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.

Event Espresso