Yes, sure, thanks. It will cost you 50$ for writing code to re-generate tickets for all registrants of existing events
However, I'm unsure how you will resend the tickets? Manually? Or automatically?
If you want it to be automatically, I'm afraid of it won't work when you have too many existing registrants (because server limit number of emails can be sent per hours, so if we still too many emails, it might be blocked by server - and being timed out, too)
Regarding e-mail (server) limits.
How does this work at the moment - if I use the "resend email" feature?
- If I do this on a large list of registrations it will be the same problem. no?
In terms of how I would want to use this feature:
I am assuming that I want to do this because I started receiving registrations with the ticket generation turned off.
I would want to turn ticket generation on for the event - so that new registrations receive a ticket and then run the tool to generate the missing tickets.
- I don't see it as a problem that the ticket numbering will not be in the order that people registered. Most of the time the tickets will (only) be collected at an event. If they are actually scanned (because they are on a persons 'phone) the number isn't important either.
- Unless someone else here has other needs ???
1. I would say that you should only resend emails for about 20 registrants at a time. Then wait for few minutes, and resend again to next 20 registrants... Also, contact your hosting provider, ask them to see if they limit number of emails per hour, if yes, how many emails?
2. I still don't understand your workflow. So even for future events, you will also start with tickets turned off, then at some point, you will turn it on? So when you want the system to generate missing tickets for the event? Maybe we will just generate it when you turn tickets from Off to On in the event setup?
From what you say I assume that Events Booking (or Membership Pro) do not "manage" the sending of e-mails (as per AcyMailing). That is - it does not batch the e-mails automatically.
- I will make a manual note to manually batch e-mails using the parameters calculated by our AcyMailing installation.
2. I don't intend to create future events without ticket generation.
this particular client first says "it's urgent" to get the event live and invitations out and only then answers my questions about whether they want ticketing. And by then people have already registered.
I try to only publish events which need tickets when the client has agreed and I have set ticketing to "yes".
Your suggestion to generate the missing tickets when ticketing is changed from "off" to "on" will probably work in most conditions.
(Unless anyone on the forum has other suggestions?)
Would this mean that if an event was started with ticketing, then ticketing was turned off, that the missing tickets would be generated when ticketing was turned on again?
In any case,
if the "new" tickets are not e-mailed automatically we will make sure that we re-issue tickets after turning on ticketing (even to those who already received them).
And, we will include a ticket download link into the reminder e-mail that we set to be sent the day before the event.