|
Avi
|
December 17, 2017 at 6:18 pm
I’m setting up an event that has both free and paid registrations (i.e., a required free ticket, plus optional paid ones). Payment can be by credit card or cheque. I thought running with two message types would work — registration pending payment (for paid registrations with cheques to be put in the mail), and registration approved (for free registrations, and for paid registrations following credit card processing). However, I run into trouble when applying a cheque payment to a transaction as I would want a registration approved message to go out, but only have the options to have a payment message sent (if I enable payment messages, my paid registrations with credit cards will receive two messages), or to have registration messages sent (which seems to generate a bunch of the wrong kinds of messages, which in any case don’t go out for various reasons).
I can only think of two ways to make this work — either forget about applying cheque payments to transactions and just “approve and notify” registrations when the cheques come in, or enable payment messages and make them exactly the same as registration approved messages — and accept that those making paid registrations with credit cards will receive two identical messages and hopefully just shrug off the duplication. Any other ideas?
|
|
Tony
|
December 18, 2017 at 6:00 am
Can you provide more details on what is happening please?
Are you manually applying the cheque as a payment in the transaction and selecting to trigger both payment and registration messages?
I don’t understand why enabling the payment email in the transaction means your online payments get additional emails? Unless I’m misunderstanding what is happening.
Which addition email types are triggered but not sent?
You can apply the payment to the transaction and trigger both the registration and payment emails when approving the registrations which it sound like you need, but it sounds like you’re already doing this?
|
|
Avi
|
December 18, 2017 at 5:36 pm
Hi Tony — thanks for the speedy reply. To be fair, I actually haven’t tested for the two e-mails thing, as I just assumed from the description of the Payment Received message that it would go out for a successful credit card payment (“This message type is used for all payment notification messages that go out including any manual payments entered by an event administrator.”) If that’s not the case, and it only goes out for other payment types, I’m all set (well, except for the bug noted in my other post, which is going to be annoying).
With regard to the additional messages triggered by the second checkbox, these in my test case were additional registration approved and registration pending payment messages without recipients or contexts, and an additional registration pending payment message with recipient and context but that just doesn’t get generated. But I don’t really care about this if I can just use the payment one and it won’t send to those making online payments.
|
|
Tony
|
December 19, 2017 at 2:53 am
To be fair, I actually haven’t tested for the two e-mails thing, as I just assumed from the description of the Payment Received message that it would go out for a successful credit card payment (“This message type is used for all payment notification messages that go out including any manual payments entered by an event administrator.”)
By default, it will be triggered by all online payments and also manual payments when the ‘payment messages’ option is checked.
So you don’t want your users to receive a payment message for online payments, only for manual ones?
The function call to trigger the messages is added via a hook so you should be able to hook in an remove the call to generate the payment messages for front end payments, something like this should do it:
add_action('init','my_deactivate_messages');
function my_deactivate_messages() {
remove_action(
'AHEE__EE_Payment_Processor__update_txn_based_on_payment',
array('EED_Messages', 'payment'),
10,
2
);
}
You can add that to a Custom Functions Plugin on your site.
|
|
Avi
|
December 19, 2017 at 7:08 pm
Yes, that’s correct. As users purchasing with a credit card will already receive an e-mail from PayPal regarding their transaction and an e-mail from Event Espresso confirming their approved registration, I don’t want to send them another about their credit card payment.
I’ll give the function you’ve suggested a shot — this will be really helpful and much more than I realistically thought would be possible when posting this question!
|
|
Tony
|
December 20, 2017 at 2:00 am
Most of the functionality in EE can be customized, it’s just finding the right way to do it 🙂
Please do let me know if the above works for you.
|
|
Avi
|
December 27, 2017 at 10:46 am
Thanks, Tony — this worked great. Much appreciated!
Avi
|
