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 Two Different Registration Confirmation E-mails | Event Espresso - Staging Server
Because my client is only accepting offline payments – is it possible to send out different registration e-mails with payment instructions? We’re using electronic transfer and purchase orders.
You can alter the default registration emails for single events within the event itself.
If you open the event and scroll down to Email Confirmation, you can either create a specific registration email within there or create one within the Email Manager (Event Espresso -> Email Manager) and select it there for that event.
If you would like to change the default registration email for all events you can do that within Event Espresso -> General Settings -> Email settings.
As it’s not a default option – we’ll consolidate the instructions in one e-mail for the moment.
It would be great to be able to send out a different e-mail per offline payment option though as the instructions for cash transfer and a purchase order are slightly different.
Would that make sense. With one you have to attach and send a PO the other you don’t.
Well, you can edit the gateway instructions via the Payment Settings page, so they can see the instructions on screen, but I understand that it would be nice to have it in email form as well. I’ll add it to the feature request list.
Viewing 4 reply threads
The support post ‘Two Different Registration Confirmation E-mails’ 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.