|
mbeede@tracom.com
|
July 13, 2021 at 10:30 am
Greetings – We are using Event Espresso to manage training classes, webinars, etc. We have been doing this since mid-2019. So our TICKET and DATE/TIME lists for each event are getting really long now. I’d like to be able to delete the list items from 2019 and 2020, or somehow get them archived and hidden from the active list of TICKETs and DATE/TIMEs. Some of these list items are actually locked now.
What can be done to clean up these lists and just have the items from 2021 appear on them?
Thanks in advance – Mark Beede
Director of IT
TRACOM Group
|
|
mbeede@tracom.com
|
July 14, 2021 at 7:43 pm
I would greatly appreciate some advice on my options to get this cleaned up!
Thanks, Mark
|
|
Tony
|
July 15, 2021 at 4:03 am
Hi there,
We don’t currently have a way to archive those tickets/datetimes from the event editor and to remove them then need to be unlocked (meaning they have no registrations assigned to them) so you would first need to manually remove the registrations linked to each of the tickets for those datetimes. However, to delete registrations you need to remove the payment(s) from within each EE_Transaction for those registrations first.
In short, each registration for those tickets would need to be edited, the payment deleted from within it and then the registration itself trashed and then perm deleted.
Do you need to keep the past registrations?
One option you can use if you don’t have registrations on upcoming events already is to duplicate the event and use the duplicate in place of the original for new registrations.
So you’d duplicate the event, edit the duplicate (which will not have any registrations assigned to it, so will allow you to edit the datetimes/tickets) so that it has you new upcoming datetimes/tickets set on that. Then, so you can use the same URL that your users already use, edit the title and slug of the original event (for example include the date or ‘archive’ in both) and update, then set the duplicate event’s title and slug to match the original. Basically replacing the original event with the duplicate.
You can then change the ‘original’ event to be privately published if preferred, you then still have the registration info if needed but have replaced the event with a ‘clean’ version.
Will that work for you?
|
