Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Payment Confirmation Email not sent for 'Send Payment Payment Received Notice" | Event Espresso - Staging Server
When I set the “Do you want to send a payment received notice to registrant” to ‘Yes’ on the Edit Attendee Payment Record form and click Update Payment, the registrant receives the “Registration Confirmation” email found in the Email Manager instead of the Payment Confirmation Email that is defined in the Email Settings section of our General Settings form.
How can I override this behavior and make sure that my Payment Confirmation Email is sent when I choose to send a payment received notice to my registrant?
Instead of using that, on the right hand side is the Invoice/Payment Reminder. You can select a predefined email from the dropdown and click send invoice and it will send that predefined email.
I’m not sure we are talking about the same thing. When someone registers for an event and chooses payment by check. The client has to manually go in and apply the payment and there’s a choice to send “Payment Received Notification” but it’s sending another email?
If you follow the instructions on this page, you shouldn’t have any issues with going from .20 to .29.1.
Viewing 7 reply threads
The support post ‘Payment Confirmation Email not sent for 'Send Payment Payment Received Notice"’ 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.