|
Matt
|
January 4, 2017 at 4:08 am
Recently we released tickets for an event and had major email issues and many people did not receive any registration confirmation, payment confirmation or ticket notices.
I’ve since got a dedicated IP and I think a much more robust email setup, but I wish to re-sent the email to everyone.
Is this possible? I have searched and I know of the Batch Email function, but that only seems to be for emails that you write yourself, not the automatic emails sent.
The only option that I can see is to go Messages > filter ticket notice > Queue for re-sending
But this will send duplicates to those who I have already done this for, which isn’t ideal.
Is there a better method?
|
|
Tony
|
January 4, 2017 at 5:48 am
Hi Matt,
How are you identifying the users that did and did not receive emails currently?
|
|
Matt
|
January 4, 2017 at 5:52 am
I have had a huge number email me asking if they should have received an email and others on social media asking.
I don’t know who had or did not have an email, but I believe a large % did not.
I think the issue is the limits placed on server emails, so this is nothing to do with event espresso, but an easy way of re-sending to all would be appreciated.
|
|
Tony
|
January 4, 2017 at 11:51 am
There is a couple of ways to resend the ticket notice email, however all of them will trigger ‘duplicate’ messages as you put:
The only option that I can see is to go Messages > filter ticket notice > Queue for re-sending
But this will send duplicates to those who I have already done this for, which isn’t ideal.
For bulk resends, filtering the messages activity tables and re-sending using the ‘Queue for resending’ bulk option is the easiest method. Any ticket notice with the checkbox selected for the bulk option will be queued for re-sending.
The other option to resend the ticket notice is through the registration list, clicking the ‘Resend Ticket Notice’ action – http://take.ms/KZ5J8
However batch processing using that method is not possible so each individual registration you want to send the ticket notice for would need to be manually re-triggered.
The only other bulk email option we currently have is to select the registrations you want to resend the ticket notice for, then in the bulk options select ‘Approve and notify registrations’. This will set the registration status to Approved and trigger the Registration Approved message, along with the ticket notice message. You need to be careful with this method as any registration you select will have the status updated (if its already Approved it remain so, if its anything else it will be marked Approved).
The problem is that I don’t know how you are going to identify the users that received the email, and the users did not, so can’t see how you are going to prevent the ‘duplicate’ emails. Any registration you select will have the emails resent, but how do you know which to select and which to not?
|
|
Matt
|
January 4, 2017 at 3:07 pm
Filtering by “accepted” entries is a possibility. If I were to do that, is there a way to edit the automatic email?
Ideally just to add a quick line of text to say why it is being re-sent?
Thanks.
|
|
Tony
|
January 4, 2017 at 4:18 pm
Filtering by “accepted” entries is a possibility.
That will send the message to all registrants so if you sent them to some those registrants will still receive this second email.
If I were to do that, is there a way to edit the automatic email?
All of the messages can be edited yes, however which specific method are you thinking of using as that will determine which message you edit and how.
|
|
Matt
|
January 5, 2017 at 2:20 am
I think I will use Resend Ticket Notice, but modify the message to say that it is a duplicated and just put some text to give a reason for possible duplicated messages.
|
|
Matt
|
January 5, 2017 at 2:21 am
I should also say – there is only one event on the website, so I appreciate that the above wouldn’t be suitable if I had multiple active events.
|
|
Tony
|
January 5, 2017 at 4:54 am
So before editing the messages I’d recommend adding a registration for yourself to the event so that you have one you can re-trigger the message on to confimr it works as expected before sending to all.
The quickest method is to edit the default message template.
Event Espresso -> Messages -> Default Message Templates -> Ticket Notice.
Edit the template to include and additional information you need.
Now re-trigger the ticket notice on your registration.
It may take a few minutes to come through as the message is generated and sent through the EE message activity tab, vist the home page on your site, wait roughly 3 mins and refresh the home page, that should be enough.
(You can also force the message to generate and send through the message activity tab – http://take.ms/3LKLr)
Is the message the one you are expecting? If so you can use the same method to trigger the registrants ticket notice.
|
|
Matt
|
January 6, 2017 at 1:13 pm
I have just tested this and the email was looking fine and would have been suitable, but I am getting a server error that I hope you might be able to give some insight into:
“Request-URI Too Large
The requested URL’s length exceeds the capacity limit for this server.”
I first tried all attendees (814), then max 400, 200, 100, 75, 50, 30 and none of those worked.
I appreciate the server is not an event espresso, but I wondered if the URL length might be affected somehow?
|
|
Tony
|
January 9, 2017 at 3:01 am
Can you post the exact steps (which filters are you using etc) you are taking so I can try and reproduce this?
As you filter the table the filters are added to the URL which will make it longer, usually that’s not a problem but if you are filtering, then filtering, then filtering then triggering messages it may me.
It could also be your host has a lower value for LimitRequestFieldSize and LimitRequestLine within Apache or large_client_header_buffers within Nginx than normal although that is rare.
|
|
Matt
|
January 9, 2017 at 2:31 pm
I tried filtering simply by selecting status to “Approved”
No category or month/year.
|
|
Tony
|
January 10, 2017 at 1:30 pm
From what context?
Can you post the full steps taken to get to the error page please?
|
|
Matt
|
January 10, 2017 at 1:35 pm
Events > Registrations > Filter: Status = Approved > Select All viewed > Approve & Notify registrations > Apply
Error message is then shown.
|
|
Tony
|
January 10, 2017 at 2:01 pm
Thank you.
I’ve tested those steps on a couple of test sites and its works fine, however the URL is long, even for small numbers of registrations.
20 registrations generates a URL over 1400 characters long which may be hitting eithrr of the two parameters I mentioned above.
Can you check with your host and see what value is set for LimitRequestFieldSize and LimitRequestLine within Apache.
If they are less than 1400 it could trigger the above and will need to be increased for the above to work.
|
|
Matt
|
January 11, 2017 at 3:43 am
Does the URL length increase as the number of attendees selected increases?
As emailing every 20 would take a very long time.
|
|
Tony
|
January 11, 2017 at 5:52 am
Yes it does, the two parameters mentioned above would need to be increased to a value that allowed you to select larger groups of registrations.
We first need to confirm that the problem is that you are currently hitting those limits on the server.
|
|
Matt
|
January 11, 2017 at 1:21 pm
The limits are set at 8190
|
|
Tony
|
January 13, 2017 at 10:20 am
Hmm, those are the default values and work fine on my test sites.
The browser you are using is not IE is it? IE will refuse the connection at ~2000 chars in the URL.
Without being able to reproduce I can’t help point you towards a way to fix or work around this.
Another option you have is to export the registrations to CSV and include the details needed to generate the ticket links within the CSV so you can use them as merge vars within MailChimp.
So you would export all registrations you want to send the email for and use the CSV to create a new list in mailchimp and import all the data.
Generate a new campaign in MailChimp with some details and generate a link using something like:
http://yourdomain.com/?ee=ee-txn-tickets-url&token=*|HTML:TICKETPARAM|*
Where TICKETPARAM is the merge var that is holding the reg_url_link value from the CSV.
Then when you send the campaign out the link should be the correct address for the tickets.
Would that work?
|
|
Matt
|
January 13, 2017 at 12:52 pm
That all sounded a bit complicated, so I figured I’d try sending again and I have absolutely no idea how, but this time it seems to have worked!
Maybe since I contacted the hosting company they adjusted the LimitRequestFieldSize and LimitRequestLine – but I really have no idea.
I sent in batches of 100 – watching emails real time, most are now through and appear to be being received.
|
|
Tony
|
January 13, 2017 at 1:59 pm
That all sounded a bit complicated
Its not as bad as it sounds, but its not simple solution by any means.
That’s strange, the error being thrown appears to be server side so it is possible the host fixed this.
Either way I’m glad its working and you got your emails sent 🙂
|
