Data protection confirmation not persisted when creating/editing an event

[alicetragedy]

After editing an event, saving it displays the following error message: “Data protection confirmation must be accepted”.
It seems like when creating an event the data protection confirmation value is somehow not persisted in the database — when editing the event again, the checkbox is always unchecked.

I discovered this while editing an already existing event, but I haven't investigated further.

[ariaru]

Thanks for reporting, I've started fixing this.
Until I'm done, please just check the terms&conditions checkbox (in those cases where the event organizers handle the selection process themselves) before saving the edited event.
[Background info: the organizers' checking the checkbox does not get persisted to the DB, it just gets validated.]

[guainumbi]

Is this still an issue that needs fixing? I checked, we still only work with validation, however this part is just applicable when we have an event where selection_by_organizer is checked. In any case it might make sense to store the consent on the db in the long run? @alicetragedy @ariaru what is your opinion on that? Otherwise, if validation is fine as it is now I suggest closing this issue.