Support

August 28, 2020 at 7:40 am

Ok, so now you have a couple of options.

You can set Event Espresso to send the emails to the ‘Event Author’ email address, which will be the address of whichever account is set as the author for each individual event (useful if you have multiple ‘event managers’).

For the above option set the ‘To’ field on the Event admin context to [EVENT_AUTHOR_EMAIL]

Or, set the Event Admin email to come from the Primary Contact Email set in Event Espresso -> General Settings -> Primary Contact Email. This is what you would use if you have the same ‘event admin’ working on all events and that’s who should be contacted for each event.

For this option use [CO_EMAIL] in the To field.

—

You mentioned you want the ability to set individual emails on specific events, so can you set the users managing those events as the event author, or do they ot have an account and you just want them to receive the emails? (Will take more work on your part per event)

August 28, 2020 at 8:28 am

Will add [CO_EMAIL]to all.
Will put me in as a cc – can i add an ohelleah email address in there – not event creator as that would be my personal email.

Sure, you can hardcode an address within the template if needed.

They do not have accounts – and what if there are 5 events at one time and different people should receive those emails?

One option is to create custom templates for each ‘person’ and hardcode their email address into each template. Then on the event(s) they should receive an email for you select the correct template with their email.

I can add more details on how to do that if it sounds like it will work for you?

September 1, 2020 at 5:53 am

TO be: [CO_EMAIL] added a cc to my ohelleah account.

Why are you setting the TO field of the Primary Registrant to be [CO_EMAIL]?

The admin ([CO_EMAIL]) is NOT the Primary Registrant so you should not be mixing up contexts with admin emails, it causes so much more confusion as there are times when admin emails send and times when Primary/Registrant email send, mixing them up like above changes everything around.

The cc came through as sent to but it did not go to the primary.

Do you see the ‘missing’ email listed in Event Espresso -> Messages -> Message activity as sent?

This should not be happening the Primary is not working at all except for showing up as the from address.

So far it sounds like you are using the contexts in a completely different manner than they are expected to be used, so I have no idea if it is ‘working’ or not.

Can someone enter the website and take a look – will set up and send access privately.

If you want one of the support team to log into the site and work through this you’ll need to purchase a support token: https://eventespresso.com/product/premium-support-token/

So far this doesn’t seem to be an issue with Event Espresso itself but rather your set up.

Sent it to the primary as a cc – address written out not a shortcode. when I had two addresses in the cc – she did not receive it – when i deleted myself as a cc – her address received the new test – this is not good….

If your sending the exact same email just to different email addresses and one works but the other does not, it’s an issue with the mailserver and not Event Espresso.

Could it be a leftover from EE3?

Not likely, no.

September 2, 2020 at 3:27 pm

I thought I was following your instructions.

Nope, please use the intended ‘context’ within a message for where it is intended to be sent.

Event admin to the event admin(s)
Primary Registrant to Primary Registrant
Registrant to the specific registrant.

I need EVERYTHING to go to the Primary Registrant – NOTHING should go to the admin. Just as it did automatically in EE3.

That is NOT how EE3 worked.

With EE3, you had a ‘registration’ email which was the email sent to whoever registered and a Admin email, which was sent to the address set in General Setting (which we consider the the Event Admin) + the CC option on the events themselves.

I think we have some crossed wires on what the Event Admin is here, by admin do you mean the site admin? As in the email saved in Dashboard -> Settings -> General?

If so thats NOT the event admin, thats the site admin.

The Event Admin (as far as Event Espresso is concerned with a default EE set up) is the email address of either the user account set as the event author OR the Primary Contact email address set in Event Espresso -> General Settings.

If it goes to the person that signed up for the event – and then it should go to the user.

?? Sorry but I don’t understand this sentence.

—-

When a person signs up to an Event, let’s call it Event A who should receive an email?

The Event Admin? (the person managing Event Espresso and has their email set in general settings)

The personal actually registering?

Another email address specific to each individual event? (they don’t have an account on the site so you were using separate message templates, right?)

September 3, 2020 at 4:12 am

OK, send me your login details so I can take a look. I’m not going to make any changes but if you’re setting it up how I’ve explained and they are going to the site admin I’ll need to see:

https://eventespresso.com/send-login-details/

September 3, 2020 at 9:44 am

Ok, please don’t make any other changes than the ones I post from this point forward. We’ll get the ‘Registration Approved’ message type working together and then you can work through the others.

First… I think you keep using ‘Primary Registrant’ in a different context to what it actually is within Event Espresso. It sounds like you are referring to the Primary Registrant as the event admin but that isn’t what it is, the Primary Registrant is the user that registered onto the event.

It depends a little on your set up but first, let’s say someone registers onto your event with a single ticket. They select the ticket and EE asks them for their ‘First Name’, ‘Last Name’ and ‘Email Address’ (+ any other questions you’ve set up). They provide them and continue the registration, the details used there become the ‘Registrant’ and as its a single ticket, they are also the ‘Primary Registrant’.

Now if you select say 3 tickets, the user submits the tickets to Event Espresso and is asked to provide 3 sets of ‘First Name’, ‘Last Name’ and ‘Email Address’ (again, if that actually happens depends on your event set up). They proceed with:

Tony Warwick – tonyexample@email.com
Bob Smith – bobexample@email.com
Carl Jones – carlexample@email.com

You now have 3 registrants in a group registration, the Primary Registrant in that context is the registrant details entered in the ‘first’ set of Personal Info questions, in the above example its me. So you have 3 registrants and one of them is also the Primary Registrant for that group.

Why do we have a ‘Primary Registrant’? Becuase that registrant is concerned by Event Espresso to be the one managing that group registration (NOT the event registration, this individaul group they register onto the event).

All of that means you should pretty much never want to swap out [EVENT_AUTHOR_EMAIL] for a REGISTRANT based shortcode. Becuase the former is an ‘admin’ shortcode intended to parse to whoever is managing the event and the latter is the (or one of the) person who registered ONTO the event.

It’s important you understand the difference here as otherwise, you’ll never get messages to work how you want them to work.

—

So now if we look at the Registration Approved message type, is has 3 ‘contexts’, which are basically individual message templates within the main type. It has:

Event Admin – This is the message intended to go to whoever is managing the event. You can set the TO field to whoever you want and we’ll do that next but the point is that the ‘Event Admin’ context should go to ‘the’ Event Admin (whoever that is).

Primary Registrant – This, as mentioned above, is the registrant EE considers the ‘Primary Registrant’ of any individual/group registrations made on your event. Its is a separate email sent specifically to the Primary Registrant and does not replace the individual ‘Registrant’ emails, which leads onto:

Registrant – each individual registration made to your event is tied to a ‘Registrant’, this is the email you should be using by default for your ‘confirmation email’ sent to the person/people registering ONTO the event.

You can see these here: https://monosnap.com/file/ezr7waWzufI1JbvUPE29ujizHbdwtC

That screenshot is from your site and shows the 3 contexts, ‘Edit Primary Registrant’ is grey because it is disabled (as expected by default).

Click on ‘Edit Event Admin’: https://monosnap.com/file/Sm2itXAZFSRySQDAIqtDD1WGrHTmrB

Notice the TO field is set to [EVENT_AUTHOR_EMAIL]? That shortcode parses to the email address of whichever account is set as the author of the specific event in question.

Change just that value to [CO_EMAIL]. That shortcode parses to the email address set in EE -> General Settings -> Primary Contact Email.

If you leave everything else on that message type is, you should have 2 emails sent when a registration is approved. One to the Registrant themselves and one to the email set in EE’s General Settings.

Now, I know I said I wouldn’t change anything but I temporarily swapped this out and added a test registration to confirm this worked. I’ve reverted this (becuase again its important you follow what is happening) and the reason I did is you mentioned above that you had already done the above but still go the emails. You can see in Event Espresso -> Messages that the emails now go to the correct emails with the setup I mentioned.

So start with the above, set up the Event Admin message context to go to the CO_EMAIL address and add a registration, once we’ve confirmed that is working how you expected we can work on changing other message templates.

September 11, 2020 at 1:55 am

Will it go out to the CO_Email as well which would be good – or does the selected custom notification override it?

The custom template is used in place of the default message templates for the event(s) they are selected on, the custom template can still go to CO_EMAIL but EE does not send both the Custom Template and the Default.

Need an edit button here – or did I miss it?

Nope, no edit button.

Forum posts being edited after they’ve been answered would likely cause more confusion than double posts so we simply don’t use edits.

My emailer does not seem to accept a comma and a second or third email address had tested that a while ago

We don’t keep login details for any longer than needed so I’ve already removed yours and can’t check this, but how is your site set to send email?

Just using your hosts PHP mail, SMTP or other?

September 11, 2020 at 3:35 am

Yeah, it’s not uncommon to run into issues with PHP mailer from various hosts.

So to clarify in the CC file are you using something like this?

email-one@example.com, email-two@example.com