|
Ian Just
|
April 13, 2018 at 2:40 am
Up until now, it has been easier to leave old events, registrations and transactions in the database.
The GDPR has changed that and there are now a couple of thousand registrations that need deleting from past events.
I could reset the EE database, but that means losing two events that I want to keep: the test one and the one that hasn’t happened yet.
Deleting non-locked registrations in bulk is doable, although it looks like I need to limit how many I do at once before I get time out errors.
But deleting locked ones means deleting their transactions and there doesn’t seem to be a quick way to do that, just one by one. And there are a thousand or so of them.
What am I missing?
I get that it’s not something you do lightly – I expect to be asked ‘do you really mean to do this?’ a couple of times – but being able to remove everyone’s details from a PAST event is something everyone in Europe is going to have to do a lot more often.
|
|
Ian Just
|
April 13, 2018 at 2:45 am
I’ve seen the post at https://eventespresso.com/topic/deleting-events-registrations-old-data/#post-249494 which says “Payments are within transactions and the developers did not build a way to delete payments in bulk” but not being able to say ‘I no longer need data from past events’ is going to make EE a very hard sell to anyone covered by the GDPR.
|
|
Ian Just
|
April 13, 2018 at 3:18 am
For those who are searching how to do this, filter registrations to give the event you want to delete the registrations from.
You can see that most have a little lock symbol underneath their ID number.
For each of them..
Click on the shopping cart symbol to the right of their details – this gets you to their transaction
Click on the trash can / bin symbol on the left hand column of the Payment Details area.
Click the delete button on the confirmation box that appears (and consider that the only good bit about all this is that ‘send related messages’ isn’t selected by default)
Click the browser’s back button (or you’ll lose the filtering)
Optionally click the browser’s refresh button, or it will still show as locked.
Repeat all this a thousand – or how ever many you have – times.
You can now trash those registrations, and then go to the trash and permanently delete them.
Think ‘it should have been possible to do this without doing four or five clicks per registration.
|
|
Ian Just
|
April 13, 2018 at 4:28 am
The other unfunny thing about this is that because the view filtering is reset after, for example, doing a bulk trash of the registrations you have cleared the transactions for..
.. it’s very easy to accidentally delete transactions from registrations from the most recent event, which you probably didn’t mean to clear out in this way.
It’s an example of how trying to protect something fails and it would have been a lot safer to have a layer or two of having type “yes, I want to delete all the registrations from the Whatever Event” before you can do so than have to do all these sodding clicks to delete registrations one by one by one by one by – oops, was that the wrong event?
Fortunately, I did want to clear out the most recent event too (the next one is setup but currently isn’t open for bookings…)
|
|
Josh
|
April 13, 2018 at 8:33 am
Hi Ian,
Thanks for taking the time to leave this valuable feedback. There are a number of open tickets to make EE4 better at deleting older data, and the developers are aware this will be a needed tool to help with GDPR compliance.
I’m going to add the feedback you left here to those tickets.
|
|
Ian Just
|
April 13, 2018 at 10:38 am
Interestingly, Firefox handles going back after deleting the transactions better than Chrome does. The one you did will still show as locked, but they other ones displayed will be the right ones
When pressing back, Chrome shows the first one you do on any page as (correctly) unlocked, but the rest of the registrations will be the wrong ones for some strange ‘browsers, whatdaya expect’ reason.
|
|
Seth Shoultes
|
April 17, 2018 at 9:22 am
Tagging GDPR
|
