Organizers and admins can currently disable registration. We want to give them the ability to restore registration.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T318412 [EPIC] Restore disabled registration | |||
Open | None | T318159 Implement ability to restore disabled registration (back-end work only) | |||
Resolved | Daan.L | T318410 Design input needed: Determine UX to restore disabled registration | |||
Resolved | Daimona | T315080 Investigation: Allow deleted registration to be restored | |||
Open | None | T318160 Implement logging of disabled registration | |||
Open | None | T321834 Implement logging of restored registration | |||
Open | None | T319237 Update language when disabling registration |
Event Timeline
From duplicate T378843:
Over on Meta-Wiki, I accidentally marked https://meta.wikimedia.org/w/index.php?title=Event:Editat%C3%B3n_sobre_Financiamiento_clim%C3%A1tico for translation without setting the page language properly. I figured the easiest way to clean up after that mistake was to tell Translate to delete the page (to clean up any traces it left behind), undelete it, set the language correctly, and then re-mark it for translation.
The result of that was that CampaignEvents deleted its records of the event, which seems to be an irreversible action (the event is still kept in the database, but there's no way on-wiki to undelete it), and on top of that I was not warned at all that I was performing an irreversible action (as opposed to standard MediaWiki page deletion, which is reversible)
The ability to do things that can't be undone is strongly contrary to the wiki way and downright scary IMO, especially with no warning.
Thank you for sharing this, @Pppery! I will talk about this with the team next week and see what can be done.
FYI the organizer of the event I accidentally deleted has recreated it as https://meta.wikimedia.org/wiki/Event:%C2%A1Edita_sobre_Financiamiento_clim%C3%A1tico!, so there's no need to do anything about that specific event, and I now know how CampaignEvents works so won't do that again, so there's no urgency this now.
Thanks, @Pppery! This is the first time we have heard of this happening, and yes, we did know that the organizer found a solution to this issue. However, I still think this is something for us to discuss as a team, since if it happened once, it could happen again. Good to know that you think there is no strict urgency to this though. Thank you for sharing this info!