|
dctc
|
February 1, 2022 at 5:45 pm
Hi,
Due to situations outside our control, we are having to postpone an event for a year. And we want to rollover the tickets to the next years event.
If we update the event datetimes to the following year, will the tickets already purchased still work and update with the new datetimes?
|
|
Tony
|
February 2, 2022 at 3:16 am
Hi there,
Yes, the tickets linked to the current DateTime will work as normal is you update the date.
I’m assuming you are just going to be changing the event start and end date? If so, the current registrations will show that new date set on the DateTime and work in the same way. However, you may want to retrigger the Registration Approved message for those registrants so they have the latest event data.
|
|
dctc
|
February 2, 2022 at 12:16 pm
That is great news. Thanks for getting back to us on that.
How do we “retrigger the Registration Approved message”? Is that a button somewhere or a php script? We have about 700 registrations to trigger.
|
|
Tony
|
February 3, 2022 at 3:26 am
Triggering messages in bulk within Event Espresso (EE) is fairly straightforward, however, you do need to be careful when doing this as your host will likely have a limit on the number of emails you can send per min/hour/day/week/month to try and prevent spam email getting them blacklisted.
I’ll tell you how to do it but the number of registrations you do this with and the frequency you do it to get all 700 done is up to you 🙂
Assuming it is for ALL the approved registrations on the event, go to the registration list for the event itself:
Event Espresso -> Events -> {hover over event} -> Registrations.
That lists all registrations regardless of the Reg Status. So at the top select the Approved status and click filter:
https://monosnap.com/file/BuTBi8aUt1YGJmvpEFplcgHCV1k1l9
That now lists the approved registrations for the whole event.
You click the bulk checkbox to select all of the registrations on the current page:
https://monosnap.com/file/iGh72vUVDYBYzFR35kKTEK4X5ebbNP
Then in the Bulk actions, you select ‘Approve and Notify Registrations’ and click Apply.
Now, just to be really clear here, what Event Espresso will do here is loop over each registration that has been selected, set the status to Approved (it should already be if you followed the above, but if not, it will change the status) and then trigger the messages related to the registration.
That’s your first ‘batch’ done, you then repeat all of the above, only before selecting the registrations and selecting the bulk action, you go to the ‘next page’:
https://monosnap.com/file/KykVApOn7H4Cj4H6szEpS97N6FX8jk
All make sense?
Side notes for this.
By default the table lists 10 items, which would be a lot of pages to work through for this. When you go to the registration list, at the top of the page you’ll see a ‘Screen Options’ tab and in that section you can set the number of registrations per page. Personally, I’d do 50 meaning you need to do the above ~14 times but should be a small enough number to not run into most limits (can’t be sure though!).
Between each batch, wait a little, again, I’d give it roughly 5/10 mins per batch but its up to you. The problem with pushing those email limits is you may not even know you’ve hit them and the server just drops the emails rather than sending them. You then only find out it happened later when you get reports of people not getting the emails… likely right before the event, so take the time to spread them out now.
|
