|
Michael
|
January 14, 2016 at 9:59 am
Hi, I made a thread a long time ago, here:
https://eventespresso.com/topic/change-messages-behavior/
I have the Ticketing plugin now, but I’m not sure I can accomplish what I’m after. Here are the 4 messages and times that I want them to go out.
at sale, to primary registration:
payment received
registration approved (not necessary)
“your tickets”
nothing else
day before event (manually with the ticket resend button):
your tickets reminder, via Registrant context (subject “your tickets ***reminder***”)
Is this possible? It looks to me like it isn’t.
|
|
Lorenzo Orlando Caum
|
January 14, 2016 at 12:46 pm
Hello,
The initial registration flow that you described sounds similar to how Event Espresso currently runs. If there are messages that you do not want to use, then you can remove the TO field from a message type and save changes and this will deactivate that specific recipient for a message type.
The re-send button uses the Registration approved message.
You could add a link so they could click to get their available tickets from that message.
Go to Event Espresso –> Messages. Then look for the Registration approved message type and click on Registrant. Then create a link and set the link to this shortcode and save changes:
[TXN_TICKETS_APPROVED_URL]
Here is a quick video:
http://cl.ly/171X2u3e322s/Screen%20Recording%202016-01-14%20at%2002.44%20PM.mov
—
Lorenzo
|
|
Michael
|
January 14, 2016 at 12:49 pm
cool video!
That’s helpful, but I don’t want Registrant to get email at time of sale. If I remove address from To: for Registrant, then I think that disables manual button re-sends.
This is the crux of it: I want to disable an automated registrant context, but retain the ability to use it manually. In other words, I want to disable the Reminder, but send it manually with the button.
|
|
Tony
|
January 15, 2016 at 6:58 am
Hi Michael,
Currently with the way the messages system works this isn’t something that can be easily achieved. It may be possible for a developer to work through and find a way to get this to work how you needed, but it would not be a simple task.
One (although not ideal) option is to disable the message type by setting the to field empty for day to day, then enabling it within another tab just before sending the message to your registrants and then finally disabling it again, however I do appreciate that’s a fair amount of tweaking around.
We have a ticket to investigate a better solution for this, likely adding a filter that can be used to check which ‘trigger’ was used to try and send the message and allow a developer to just hook in an stop specific triggers/messages. I’ve added this thread to that ticket and we will update this thread with any news.
I should add that currently we are working through improvements to the messages system, once they are finished would be the best time to add this function so it may take a little before we get this out.
|
|
Michael
|
January 15, 2016 at 7:28 am
Thanks for reading and thinking about this. This kind of detail is helpful, because I was thinking of searching the code for something to comment out.
Also want to mention that we’ve been very happy with EE, EE4, and responsive support like this.
In the last 13 months, we’ve put up 1,685 events with EE.
|
|
Tony
|
January 18, 2016 at 3:17 am
Thank you for the feedback Michael 🙂
I’m glad EE is working well for you, that’s roughly 130 events per month…. nice job!
Would you be interested in sharing you experience with Event Espresso? If so take a look here at some options:
https://eventespresso.com/about/help-us-help-you-how-to-share-event-espresso/
Please let us know if you have any problems at all.
|
