Posted: February 7, 2020 at 4:21 am
I can’t seem to find the right code for sending out the confirmation email to all registrants.
I’ve tried: [RECIPIENT_EMAIL]
So which code should I use in order for the confirmation mail to reach every registrant?
As you referenced the ‘confirmation email’ I’m assuming you are referring to the ‘Registration Approved’ message template.
If you want an email sent to each registrant you want to edit the ‘Registrant’ context.
Event Espresso -> Messages -> Default message templates -> Registration Approved -> Edit Registrant.
The ‘To’ field should be
(Note that this is the Event Espresso default setup for this message type already)
The Primary Registrant is still a registrant and will receive the registrant context, the ‘Primary Registrant’ context should only be used for additional email containing further information or as the sole email sent rather than an email for each registrant.
How are you collecting the additional registrant details on the registration form?
Is there an event I can run a test registration on to view the setup?
Thank you. Your event setup looks fine.
With the above, which ‘context’ (see HERE) are you editing on the message type?
On the ‘Registration Approved’ message type there are 3:
The Event Admin obviously just goes to the the admin.
Primary Registrant should be used for messages that you want to go to the Primary Registrant.
The Registrant context is looped over for each registrant in the group and the templates is used to generate a message for each individual registrant (which is what you want).
It could be that you have the ‘Primary Registrant’ context active, but the ‘Registrant’ context de-activated.
(Note the above is all based on the default behaviour, if you’ve changed the templates at all you may have changed this)
Can you post a screenshot of your Registration Approved message type listed in Event Espresso -> Messages -> Default message templates.
The important part is that ‘Registrant’ is not grey and looks like the screenshot.
Click on the ‘Edit Registrant’ link and post a screenshot that page, please.
The top of the page above the fold is fine, I just need to see the page header and the ‘to’ and ‘from’ fields.
So I just tested a group registration with 3 tickets the messages sent as expected:
3 Registrant emails (as there is a total of 3, 1 Primary and 2 additional)
Note if you are using the same details for each registration on checkout EE tries to reduce the number of emails and so it will simply send 1 registrant as they are all exactly the same.
I just tested this again and for a group of 4 tickets, I’m getting 5 emails.
4 x the registrant email
You’ll obviously get the Event Admin email and so far this appears to be working as expected.
If you go to Event Espresso -> Messages -> Message activity, can you see the messages there?
I’m not sure what you would be doing differently to get a missing email, but as a registrant (and also the primary registrant) I’m getting all of the expected emails from your site.
So the emails showing in Message activity log means that EE is correctly triggering and ‘sending’ those emails.
When EE sends an email what it does is build out the content in the messaging system and then to send it passes them to wp_mail() which basically checks for various headers and tries to confirm the email is set up as it should be before passing it off to your server to do whatever you server is set up to do with emails.
All of that means that if the email shows as sent in EE, then
There are 1001 reasons mail servers can flag an email as spam randing from the content of the email (EE uses HTML emails which may well be flagged by the mail server for the domain) to the IP address of the sending server.
When users run into deliverability issues like this we recommend switching to a transaction email server:
Using one of the above services fixes the issue 99% of the time.
The support post ‘Code for sending confirmation mail to all registrants’ 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.