Support

March 20, 2019 at 6:29 am

Hi there,

1. My site is live. Problem is tickets are mailed before tickets are paid for. HELP Please.

Tickets are sent when the registrations are Approved, by default that happens when full payment is made using and online payment method.

Or, if you have set the ‘Default Registration Status’ to ‘Approved’ that basically tells EE you don’t care about payment status, all registrations apply to the evemt.

So if you edit the event and look in the ‘Event Registration Options’ what is set there currently? (Most user want that to be ‘Pending Payment’)

2. If person orders 2 tickets I have 2 entries on my registration page.

That’s correct, 1 ticket == 1 registration.

3. Can you customize the registration page, add custom fields at a glance so you do not have to go into the properties of the item.

You mean the admin registration list? (Event Espresso -> Registrations)

If so, yes you can add additional custom fields, but it needs to be done via code. I can give you an example if you are comfortable with PHP?

March 22, 2019 at 10:21 am

I do not feel you answered any of my problems.

I’m sorry you feel that way.

My registration status is Approved the other option DO NOT WORK

Because you have the Default Registration Status set to Approved, you are telling EE to send the tickets regardless of payment and that’s expected behaviour with that setting set to Approved.

In what way do the other options not work?

That is NOT correct 2 tickets = 2 registrations.

It is correct.

1 ticket == 1 registration
2 tickets == 2 registrations
3 tickets == 3 registrations
and so on.

Each ticket creates a registration in Event Espresso so when you select 4 tickets, EE generates 4 registrations.

May I ask how it would work if selecting say 4 tickets generated 1 registration but you wanted to collect the details for each individual attending the ticket? In short, each ticket needs to be a separate registration in the system for it to cover all use cases.

This problem needs work there are things that just do not work

Such as? There are no details of what apparently isn’t working.

All of the above sounds like expected behaviour with the settings you are using. I’m happy to investigate any issues you’re having, but you’ll need to provide more details.

Changing the custom fields just be not PHP you should be able to change within the program.

Currently, that’s not an option.

With the various different field types people want may to add to the page, the best solution is to use code for each specific use case.

March 22, 2019 at 10:37 am

OK 2 tickets = 2 transactions I get this is how you coded it and cannot be changes. Hope its improved for future.

2 Registrations, not 2 Transactions.

Every ticket creates a registration but a group of tickets selected in a single group, are all linked to a single transaction.

We are not looking to change that setup in the future, I’m not sure why it needs to be changed?

payment set to approved, when I set to no approved. People had to go back and reregister and it looped so not a nice feature if no one can get to payment.

Not Approved is the wrong status to use for your use case.

Not approved means th admin needs to review each registration and chang the status to ‘Pending Payment’ or ‘Approved’ to allow payment. You can thing of that setting as ‘Pre-Approval’, someone registers, the admin checks they meet the criteria and then allows payment.

I am worried to try pending payment since my site is live. How will that process payments vs approved that I have selected.

Set the status to Pending Payment, its the default setting for Event Espresso and is the option most people want to use.

With pending payment the user can run through the registrations and pay in the same way they are now. The difference is that registrations that do not complete payment using an online payment method with not be automatically approved (people paying online with one of EE payment methods will still be automatically approved).

Lastly custom fields hope you guys put on your future updates to include changes to the registration list

Again, this is unlikely due to the sheer number of different fields types people may want to add, any options we added for that would just cause more confusion. If you want custom fields on that section, you’ll need custom development to add them, we have filters in place to make this fairly simple for a competent developer.