Support

January 17, 2024 at 2:37 pm

Hi there,

Yes, it is likely possible to prevent just the admin emails but I’m a little confused by your setup currently so I’ll need some details to work through this further.

We’re getting one email for the registration confirmation and then one each for the registration plus any add ons they purchase

How are you setting up ‘add-ons’ within EE?

…is there a way to disable the payment confirmation to admin only?

It depends on the specific email you are getting, with only 2 of those showing in the logs it seems strange you are getting more. The standard Payment Received email can be disabled in:

Event Espresso -> Messages -> Default Message Templates -> Payment Received.

You want to edit the ‘Event Admin’ context and set the ‘To’ field to be empty, and/or click the toggle switch at the top of the message to disable it: https://monosnap.com/file/WxwlvX2l632mOmTqOx2705a8FCQ7Xn

To clarify; I still want registrants to get their payment confirmation email but do not want to see multiple emails in our inbox for payments.

This is the part that gets a little confusing as their shouldn’t be multiple emails for this.

Can you link me to an event I can view you setup on?

Can you add some screenshots of the emails you get, or forward them over to support@eventespresso.com so I cant take a look.

January 18, 2024 at 3:44 pm

Hmm, strange.

You shouldn’t be getting a payment received email for every ticket.

That’s basically a group registration (you’re not using it as such, but within EE that’s what it is) so you should only have 1 payment received email for the transaction as a whole.

Did the above make any difference?

January 22, 2024 at 6:24 am

when I updated to 5.0.11 I had to go in and verify a bunch of things to make the reg page functional; didn’t take much time but I just need to know if every time I update EE will I have to go in and verify all those settings or was it just because we did a major update from 4.x to 5.x?

Something within EE told you to do that?

Generally, we have 3 types of releases… Major, Minor and Patch.

X.0.0 release would be a major release

5.X.0 would be minor release

5.0.XX would be patch release

‘Major’ releases are going to be relatively big changes, like EE3 -> EE4 (which was very big) or EE4 -> EE5 (introduced the new advanced editor).

‘Minor’ releases can still actually have relatively ‘big’ changes, but those are going to be feature-related releases. So we may add a completely new feature between 5.0.XX and 5.1.XX. If we release a minor version, it often means there has been a change in how the database is structured or the data is saved etc and we run a ‘migration’.

For the 2 above it’s a good idea to do a database backup before updating (you should do for every update, but the above have changes to the DB so you should create a backup before doing them).

Running through all of your settings isn’t usually required although it won’t hurt.

—

Patch releases are most often bug fixes and small features implemented/changed.

I recommend after each update to run through a quick test registration just to confirm those work as expected (your registrations are the important part of EE, right?). You’ll often know pretty quick if there is an issue within the admin as it’ll either fatal or show nothing.

The above update you’re referring to is a patch update, 5.0.11p -> 5.0.15p (.15 is not the latest as we had to push a fix for SiteGround). I’d run a quick registration test after the update but wouldn’t go through all my settings, I’m not going to tell you NOT to as any update (no matter how small) can cause issues, especially with the millions of combinations of plugins people can have. But out of all the types of updates, patch updates are usually the ‘safest’.

January 23, 2024 at 4:42 am

We are glad you got that working now. Please feel free to ask if you have any other questions.