|
Michael King
|
May 19, 2019 at 10:24 am
I know this has been asked and answered – many times, but I’m still seeing to understand. I’ve been using EE4 for a few years now – typically 2-4 events per year, 300-600 people per event. That means I have thousands of registration records doing me no good, and taking up disk space, which impacts my backup time and space. So ok, I don’t “need” to delete the old, but I’d like to.
I understand I can delete an old event if I first o – n – e — b – y — o – n – e delete all the transactions to unlock the registrations, and then delete the registrations. I think we all know that’s unworkable. And yes, I know, we don’t want to make deleting registrations and events too easy.
I guess I’m making a plea for some kind of house cleaning or garbage collection function that could do something with the old. Or at least an explanation for why there isn’t a practical way to delete old events.
|
|
Josh
|
May 20, 2019 at 3:54 pm
Hi,
There isn’t currently a practical way to delete old events because what would happen is the database would end up with orphaned data. For example, if you deleted one event, then 300-600 attendee records and all of the associated data (registration form answers, payments, line items) would no longer be connected to an event.
To avoid this, the plan is to build out a system to cascade delete related entities. So for example if you wanted to delete all records of payments, registrations, datetimes, tickets, line items, registration form answers, and transactions associated with an event, the cascade delete would go through and delete only what’s related to that event (and nothing else).
With this cascade delete feature there are few challenges that would need to be worked out, for example: What happens to transactions that have multiple events where one event is to be deleted and one event needs to remain? Also, would attendee records also need to be deleted if all related registrations are deleted?
What you could do instead (and some have done) is set up a sub site for a year or so’s worth of events & registrations. Once that year is over, then take a backup, delete the site, and set up a redirect to the new years site. This way your database of events & registrations only go back until the beginning of the current year.
|
|
Michael King
|
May 22, 2019 at 2:11 pm
Hi Josh,
If you’re looking for feedback on the cascade delete idea, here’s mine. Basically sounds like a fine solution. Thanks for the insight!
The nature of what I do doesn’t create transactions associated to multiple events, so no problem with that. I don’t use attendee recording, but I’d think if I was deleting an event, I’d be happy to delete the attendance record as a part of the housecleaning, especially so if I had a chance to download the attendee records first.
i understand the idea of setting up a sub site for events but I prefer to keep things all under one URL for user experience. And what about duplicating events, something I do regularly, between sub sites? Sounds messy; I’d rather live with the long list of old events.
mk
|
