Posted: August 21, 2022 at 10:55 am
|
After overhauling my email sending and custom templates my primary registrants also get the registrant confirmation messages, ie Primary gets 2 messages. I don’t recall that being the case in the past, it’s creating some confusion, and causes me to be sending about a third more emails than I really need. I could not find anything in the EE4 docs that addressed this or this level of detail. I saw some posts about this in the support forum from the 2015-2017 time frame – responses seemed to belong the lines ‘the primary is still a registrant, so that’s the way it is – deal with it’ which didn’t seem very helpful. So is that really just the way it is and always has been? Or has something changed in the last 5 years? Is there anything I can do to change this behavior? What if I added [recipient email] to the To or CC fields on the primary registrant message, and had no [recipient email] on the recipient context? And how does the messenger know to send a message to all of the [recipient email] registrants> Help? How does the me |
|
|
Hi Michael,
It’s never really been a case of just ‘deal with it’ but if the system is designed to do X and a user wants it to do Y we can’t simply change the whole system to suit every time that happens, it would literally never end. If we don’t have an option for whatever is being requested and it isn’t something we can provide a snippet to help bend the system to do then ultimately the answer will be ‘it can do X’ because that’s how it’s designed to work. We do have a lot of hooks within which can allow you to change the behaviour with custom code, although you’ll need the help of a developer and the messaging system has a log of cogs to turn so it’s not easily done.
In that the Primary Registratant context will send as an additional email? Yes, it has always been that way.
No.
Not easily, no. Possible, yes, but additional functionality within the messaging system is not something we provide support for.
Then the primary registrant would receive 2 emails as at the time of processing they will be the recipient. Removing the shortcode (or value) from the To field will disable a message type/context.
The messenger builds up the data it needs before starting to generate the message(s) For example it will pull in the Primary Registrant on its own, all of the registrants for the group into an array along with a bunch of other data. Then the registrant context loops over each of the registrants and generates a message for each registrant in the group, the primary registrant content generates using the data specifically for the primary registrant. It sounds like you need to disable the Primary Registrant context and use registrant, if you need additional information that should go only to the Primary Registrant you enable that context. Whats the use case you are running here? |
|
|
First, my original question now sounds more harsh than I intended – I’m sorry, it was the end of a long weekend at the keyboard. Apparently our email was previously more unreliable than I knew and/or no one ever noticed primary registrants were getting two messages. Neither time nor budget nor real justification for for custom code, so we we will work with what you give us. Our use case is selling reservations for a symposium about suicide prevention. We expect the topic will mean more single registrations than our usual events with topics that are more fun and get a lot of multiple registrations. That has highlighted for ‘the management’ what happens with the primary registrant, and I got a bunch of questions/complaints about the situation. As I now understand things, if I take addresses out of the To field in the Primary context everyone will just get the registrant context message and there won’t be any issues or duplicates? Or if I use only [registrant email] in the Primary context and blank the Registration context, everyone would get the long primary version? FWIW, your docs occasionally refer to disabling a message context, which had me looking for a switch, button, preference or something. Didn’t dawn on me until later last night that if there is no address(es) in a context, nothing would go out. Thanks again! |
|
No apology needed 🙂
The primary registrant message context is not enabled by default, so could it may be that is has now been enabled by mistake?
I assume this is for the Registration Approved message type, yes? If you disable the Primary Registrant context and leave the Registrant enabled (which is the default setup for that message type) then yes, everyone in a group or single registration will receive one email for that message type.
No, if you do this then only one email will be sent out, using that shortcode at that specific time will likely go to the primary registrant becuase they ‘are’ the registrant at that specific point. The ‘context’ of a message type is how EE intends to use it. So the Primary Registrant context for example is set up with the data specific to the primary registrant. You ‘could’ switch out the message shortcodes for a registrant one but that context is still only intended to be generated against the primary registrant meaning one per group. The Primary Registrant context should be used as an email sent ONLY to the primary registrant. The Registrant context is one that is sent to EACH registrant within a group (including the Primary), EE knows to loop over each registrant to send that email. The shortcodes are parsed specifically for each individual registrant as the message is generated. So if you want everyone to receive a registration-approved email, use the Registrant context. If you don’t want an additional (or in your case yours is set up as a duplicate) email specifically sent to the Primary Registrant, disable the Primary Registrant context.
So, message contexts do actually have a toggle… but can also be disabled using the TO field. Originally the message system did not have a toggle for each specific context, to disable it you had to empty the TO field. We then added a toggle switch to each one, but still work. Toggle enabled – https://monosnap.com/file/tNlsfGV6wGFPyfLuOOtR6mmLkFCc2V Toggle enabled but empty To field (disabled) – https://monosnap.com/file/BSXVi9AWmzxclsEN55joQgNbaSrg4V We have to support both methods of disabling the context currently to make sure things work smoothly for everyone. |
|
|
Ok, I think I have this now. I took the [primary… out of the TO in the Registration Approved message. After doing that I got a little warning box saying “Please fill out this field” but I just ignored that and the [primary… shortcode came back. What’s up with that? |
|
|
Part 2… |
|
|
Part 2…and them I realized what the switch for active/inactive does and just turned the Primary context for Reg Approved OFF. I thought that was just some indicator for which context I was looking at. I’m going to stop fiddling with this now – we are live and I don’t what to screw something up. Thanks again. |
|
Sounds like your browser’s validation is kicking in and preventing the submission when empty, I’ll create a ticket for us to investigate this further.
Yes, it will, but I don’t recommend doing so, however, you’ve already figured out how to disable the context with the toggle now 🙂
Yeah, the toggle will disable the specific context you are viewing so should stop the ‘duplicate’ email you are seeing. |
|
The support post ‘Primary Registrant also gets Registrant email’ 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.
