|
Paul Doyle
|
September 3, 2014 at 8:25 am
I am using the Invoice payment option as well as Paypal. I have it defaulted to “Approved” so the Invoice bookings are counted towards the ticket limit. However having the Invoice booking “approved” mean that is sends out the Approved email rather than the Payment Pending email… Is there a way to count Incomplete bookings for the ticket limits? .. I hope that makes sense.
|
|
Jonathan Wilson
|
September 3, 2014 at 3:08 pm
Hi Paul,
If you set the default payment status to Pending, it should count toward the numbers, but not send the Approval email. Incomplete will not count toward the numbers.
|
|
Paul Doyle
|
September 7, 2014 at 1:06 pm
Hi Jonathan, thanks for the reply …
Are you referring to “Default Registration Status”? if so the 3 options are “Approved”, “Not Approved”, “Pending Payment”…. Pending Payment does not reduce the number of available tickets.. Or are you talking about something else?
|
|
Dean
|
September 8, 2014 at 2:37 am
Hi Paul,
Sorry for the confusion, Jonathan was referring to EE3 not EE4.
Currently the only way to count an incomplete booking to the ticket limit is to set them as Approved.
I see what you are saying about the emails though, the registration approved goes out instead of the pending payment.
I will start an internal discussion about this.
|
|
Paul Doyle
|
September 8, 2014 at 3:08 am
Hi Dean,
Great thanks.
-Paul
|
|
Josh
|
September 9, 2014 at 2:08 pm
Hi Paul,
There are going to be a few changes to how messages work in Event Espresso 4.5 that will open up some flexibility for adding payment reminders within different message types.
In the meantime, I can suggest changing the default behavior of the payment reminder message type so that when someone selects the Invoice payment method they’ll automatically get a Payment reminder email. The payment reminder email can include a message that contains a link to the invoice and even information that lets them know their seat will be reserved for up to x many days if need be.
Here’s a code snippet that will work for Event Espresso 4.3 & Event Espresso 4.4 that can be added to a functions.php file or a little site functionality plugin.
https://gist.github.com/joshfeck/bc4a1612a7296b3dc028
What the above code will do is change Event Espresso 4 so it automatically sends a payment reminder when when the Invoice method is selected for payment.
|
|
Paul Doyle
|
September 9, 2014 at 3:20 pm
Hi Josh,
Thanks for the reply and code.
I’m a little confused tho. What should I set the “Default Registration Status” to?
“Approved” is the only way to be counted as a confirmed ticket and thus reduce the available tickets right??
So if someone selects Invoice payment will the “Approved” email not be sent now and the Payment reminder sent instead?
Just for context …. We are using the Invoice option to allow people to pay cash at the door. But we want to fully confirmed them on the system at the time of booking. It’s not the end of the world to use the “Approved” email for everyone but I would be better to have separate emails as the text needed in each is a little different.
Sorry I hope all that is clear … Thanks again for your time and response.
|
|
Paul Doyle
|
September 9, 2014 at 3:26 pm
Actually to be more precise, I said … “we want to fully confirmed them on the system at the time of booking”…. but that is just because a pending registration doesn’t reduce the ticket numbers available.
We actually just need a “payment pending” to be subtracted from the available tickets (automatically)… that would solve all our problems. Is there a way to do that?
|
|
Josh
|
September 10, 2014 at 9:04 am
Hi Paul,
You’re correct, the Approved status is the only status that will automatically deduct an available seat. That’s the default status to use in this case.
If you add the code I posted to your theme’s functions.php file or into a little site functionality plugin, it will automatically send the Payment reminder along with the Approved message. In order to help prevent confusion, it’d be a good idea to add a remark in each of these messages that automatically go out that their registration is confirmed but if they do not pay online, they’ll need to pay at the door.
I’ll repost the built in documentation for the Default Registration Status here as it explains the differences between each of the statuses:
Approved
A status of Approved means that a registration has been accepted as complete. The registration will count towards the registration limit, remaining tickets, and calculations for available seats. Payments (if necessary) can also be made by primary registrants with this status.
Pending Payment
A status of Pending Payment means that a registration has not paid but they ARE able to make payments (if necessary). Pending Payment registrations do NOT count towards registration limits, remaining tickets, and calculations for available seats. If registration for a free event occurs, then registrations are automatically set to Approved. For paid tickets, Pending Payment registrations are set to Approved when full payment is recorded.
Not Approved
A status of Not Approved means that a registration has not paid and they cannot make payments for towards an event. Un-approved registrations do NOT count towards registration limits, remaining tickets, and calculations for available seats. This setting differs from the “PENDING PAYMENT” default in that free ticket registrations and paid in full ticket registrations do NOT automatically switch the Registration to APPROVED. Instead, the event admin must manually set the registration to either “PENDING PAYMENT” for registrations requiring payments, or “APPROVED” for free events.
|
|
Paul Doyle
|
September 10, 2014 at 9:24 am
Hi Josh,
Thanks for all that. I think in this instance we will just include both paragraphs of text “if you chose PayPal” …. blah blah and “If you chose At The Door” … blah blah … in the Approved email, rather than sending a second email
Thanks again for you replies.
|
