Posted: July 27, 2019 at 12:24 pm
Hi, I have two events, both with a different custom ticket notice. Event Espresso – 4.9.77.p – Gural |
|
Hi Gural, May I ask for some clarification? Was the ticket notice set to be custom for the event, or was it the actual ticket? |
|
for the event… |
|
I was actually asking if you had set a custom ticket This is a screenshot of the setting for a custom ticket notice: and this is a screenshot of the setting for a custom ticket: |
|
I use a custom ticket notice (your first link) (btw, it might be good to display directly if a template is (not)active in main event settings page, instead of having to open it first… as far as I can see everything is configured correctly.. |
|
Hi, If you test a registration for the event in question, do you get the correct ticket notice? |
|
Hi, I tried a new test event (in private mode), with the same settings, but that doesn’t seem to work in terms of getting mails. But I do get the same issue when viewing the ticket notice message at the backend, i.e. I go te registrations – view related messages The options for the ticket notice are Pondering… and / or (2) the fact that we are using the copy event method to republish recurring events……. |
|
The issue wouldn’t be related to either 1 or 2. It could be a context-related issue. You could go to Registrations > View related messages and under the context column it will show which context was sent. Was it the Primary Registrant context or the Registrant context? Then go to edit the custom ticket notice template and edit the context that was sent, doe it have the correct contents? |
|
oke, It says for the context ticket notice: Registrant do I need to change that to registrant instead? (btw, the test mail from the previous message came in, just took some more time apparently) |
|
You can use either or even both contexts. The important thing is whichever contexts you choose to send, you’ll want to make sure the template has the correct contents. |
|
Wil check this.. |
|
A bit confusing, but I see that you can edit the message for each recipient in the messages settings.. |
|
May I ask, how else you would prefer we handled the above so it wasn’t confusing? Each message type has multiple ‘contexts’ in which it’s used, so in this example it is the ticket notice which has a ‘Primary Registrant’ and ‘Registrant’ context. That’s a little more niche so let’s use the ‘Registration Approved’ message type as an example as its more general, that has an ‘Event Admin’, ‘Primary Registrant’ (this context is disabled by default) and ‘Registrant’ context. When a registration is Approved that message type can send different content to each of those contexts and you’ll likely want different content for the Event Admin than the Registrant (which is why we have ‘contexts’). The other way to offer that flexibility is to separate them all out into individual templates, which means rather than the 13 message types we normally have by default we’d have 23, plus any additional templates/contexts added by add-ons, I imagine the notification section used to allow you to select specific message types on an event would then end up more confusing than the above. If you have any feedback on how we can improve the above I’ll pass it along to the developers so we can try and make it a little less confusing. |
|
I had two active events, with two different custom ticket notice messages. There are a lot of settings in EE, perhaps a kind of message dashboard / table page (without dropdown.. showing the current set configuration (each active message for each role, might help new users intuitively fix any wrong messages) A “button” linking to it “Check your current message settings” don’t know.., thanks for helping out. |
|
I’m not sure how that table would fix the issue of misunderstood contexts as it would basically show the message type and even if we display the active contexts for that message type it’s the same as what they see in the messages section. We know from experience that users generally won’t click through to view the above (there’s various help sections already built into EE which many users don’t use) and those that do are the types of users that would have already gone through the documentation and be aware of message contexts, so I’m not sure an additional ‘Check X, Y and Z’ overview is the way to go for this. However, we do appreciate your reply/feedback and have noted your suggestion. |
|
The support post ‘Custom Ticket Notice / wrong receiver’ 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.