|
utahhockey
|
September 26, 2015 at 3:51 pm
We have several individuals who purchase multiple tickets under the same email address, for a single event. We use the Newsletter Messages type to get them there tickets on the day of the event. However, we would like to use the [EVENT_LIST], [ATTENDEE_LIST] *:, [TICKET_LIST] *:, [DATETIME_LIST] *: optionally on the Newsletter Message type.
Alternatively we could use a custom template however, we cannot figure out how to create a custom message to the Registrant the above fields.
The end goal is to email everyone their individual tickets for every event and for those individual who registered themselves 4 times to get 4 emails.
|
|
Tony
|
September 28, 2015 at 5:17 am
Hi there,
The end goal is to email everyone their individual tickets for every event and for those individual who registered themselves 4 times to get 4 emails.
The newsletter message type is contact based, so if a user registers 4 times with the same details that makes 1 contact assigned to 4 registrations. They would receive a single email in that situation.
If that 1 contact received a single email, that listed all of the tickets would that work?
|
|
utahhockey
|
September 28, 2015 at 10:01 pm
Yes that is exactly what we’re looking for.
|
|
Josh
|
October 1, 2015 at 11:57 am
Thanks for taking the time to leave this valuable feedback. I’ve registered your suggestion and we will keep it in mind for future features and updates!
|
|
utahhockey
|
October 1, 2015 at 12:32 pm
Josh,
This isn’t a feature request or feedback, it is a MAJOR bug. The majority of ticket purchasers are not receiving their tickets. Combined with the system sending LAST YEARS tickets to our customers, we currently have a ticketing system with less function than last years version of EE.
Please elevate this to Garth or Seth because
|
|
Seth Shoultes
|
October 1, 2015 at 1:37 pm
AJ,
We’ve been made aware of the issue, but there’s little we can do in less than 24 hours.
Here’s what needs to happen:
- Developers stop working on current issues/projects
- Track down the cause of the issue
- Fix said issue
- Send to another developer for code review
- Support team tests the issues
- If no other issue are found, it will be merged into a stable branch
- More testing will be done to make sure it doesn’t break other areas of the system, once it’s integrated with the core system
- If no other issues are found, then it will released into the wild
Your still looking at at least a week, or longer before this would be released. I’m not sure how we can speed this process up, especially since this is the first time hearing about it, and our developers are already working on other higher priority issues/projects, and we’re coming up on a weekend.
I’m sorry you’ve found this issue so late in the game, but there is little we can do RIGHT NOW. We’ve tried to make a robust solution, but it seems that it may not be what you truly need. It may be best to start looking for an alternative solution, or build your own custom solution.
|
|
utahhockey
|
October 1, 2015 at 5:33 pm
Seth, thanks for the explaination, appreciate it.
And to be clear, We are well aware things take time and am fully supportive of that. Also, we are fine waiting our turn in the support que.
I think the canned “we will keep it in mind for future features” wasn’t taken well as we are using the system as we were told to do so.
We’ve been a long time customer of EE and am really surprised that you are suggesting we look for alternatives because we are reporting bugs.
Thanks.
|
|
utahhockey
|
October 1, 2015 at 5:40 pm
Seth,
One other thing, the ‘Registration Approved’ message is totally functional and works totally as desired. This request was made because we thought we were missing something in the Messages portion of EE when we tried to send reminder messages to all registrants. Unfortunately, only the primary registrant is receiving the emails…
|
|
Tony
|
October 2, 2015 at 4:08 am
Hi AJ,
The comment Josh made regarding feedback was in relation to adjusting the newsletter message type to be able to use Event based shortcodes such as:
[EVENT_LIST], [ATTENDEE_LIST] *:, [TICKET_LIST] *:, [DATETIME_LIST] *:
This completely changes how the newsletter messenger would need to work, it is currently designed to be used as a contact base messenger, as in you are sending a message to the contacts of the selected registrations. So EE pulls all the information for that contact and sends the message to them, however a contact can have multiple registrations assigned to it and those registrations can be across multiple events. So building the message based on the contact itself means EE doesn’t know which registration/event that specific message was for, therefor Event based shortcodes can’t be used right now in.
I’m trying not to get into too much detail but basically to switch the messenger to use those shortcodes it needs to no longer base the message on contacts, but on registrations for the event, like the Reg Approved message is. This isn’t a simple task and has other ramifications that we must take into consideration, for example we (EE) control all instances of when a Reg Approved message is sent so it can be specifically tailored to suit, with a newsletter message type we do not control how/when/why the message is sent and so takes much more planning to get right.
Your current issue with [RECIPIENT_TICKET_URL] displaying previous tickets, from your other thread here:
https://eventespresso.com/topic/newsletter-email-sending-previous-event-download-url/
Is an example of how a shortcode is used within a messenger in a way that we just didn’t expect but it isn’t related to allowing Event based shortcodes (due to the above) to be used within the newsletter messages, which is why this was considered a feature request/feedback on the current messenger, I’m sorry if that come across differently.
So having said all that, I think I may have a work around to get your tickets to send using a custom Reg Approved message which I will now add to your other thread.
|
