|
Caitlyn Fagan
|
November 3, 2015 at 4:35 pm
Hi,
I was wondering if there would be any repercussions that affect the registration or transaction records if I delete expired available tickets from a recurring event.
|
|
Lorenzo Orlando Caum
|
November 3, 2015 at 4:56 pm
Hi Caitlyn,
Event Espresso 4 will lock any tickets which already have registrant/attendee information linked to them.
If you are wanting to hide expired tickets from the ticket selector, then there is an option that will remove those for you in Event Espresso –> Events –> Templates –> Ticket Selector Template Settings:
http://cl.ly/image/1r1R33203t0S
—
Lorenzo
|
|
Caitlyn Fagan
|
November 4, 2015 at 9:21 am
Hi Lorenzo,
It appears that Event Espresso 4 locks the Event Datetimes that are associated with registration and transaction information, but it does not lock the tickets that were created to be associated with the event datetime.
Do you know if it is safe to delete the expired tickets, that are associated with the locked event time?
The reason I am asking is because on our recurring events, on the backend of WordPress on the individual event page, we keep getting the error message the we keep hitting our max_input_var message. We’ve already increased the max input var amount several times, and so I was hoping that if we could delete these expired tickets that it could help with this issue.
|
|
Lorenzo Orlando Caum
|
November 4, 2015 at 9:34 am
Hi, if you have the option to delete, then you can do so.
If there is a lock, then Event Espresso won’t let you delete to prevent a loss of data.
The max input vars is a symptom that the event may have too many datetimes and tickets. This usually starts at about 15 to 20 ticket & datetime options but may vary between shared hosting platforms.
If you have many ticket options, then consider picking up the multiple event registration add-on as it will let your attendees/registrants register for multiple events at once which means you can break up tickets across different events.
—
Lorenzo
|
