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 When is the Default Registration Confirmation Email used? | Event Espresso - Staging Server
When is the Default Registration Confirmation Email used?
If “Send registration confirmation emails before payment is received?” is set to “No,” what is the purpose of the registration confirmation email?
Upon initial registration, I would like my attendees to get a “registration confirmation” email with a specific notice that their seat is not reserved until payment is received. Is this not recommended?
The registration confirmation email is sent to the registrants to advise them that they have succesfully registered.
Some people do not want this email to go out before payment has been confirmed, as such if “Send registration confirmation emails before payment is received?” is set to “No” the emails will only go out after payment.
Upon initial registration, I would like my attendees to get a “registration confirmation” email with a specific notice that their seat is not reserved until payment is received. Is this not recommended?
Well, those who register – paid and not paid – will get the same email, so if you don’t mind users who have paid getting that notification then it is fine.
Looks good to me but the content of your emails is, as always, up to yourself.
Viewing 3 reply threads
The support post ‘When is the Default Registration Confirmation Email used?’ 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.