You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whatever time we choose as a cutoff point, we should stop accepting submissions and edits-- refuse CollectController#creates/updates, redirect the edit links to go to show, and have a "sorry, we're closed!" action or something.
For short term fixes, we could have someone manually deploy a change or turn off the dynos or something at that time.
A neater, more sustainable fix would be to have a datetime setting on the event and make that change automatically.
The text was updated successfully, but these errors were encountered:
There's already simple crud controls for Events hiding in the Control controller (ugh, I know). It'd be pretty trivial to either set an expiry date or just have a big off switch for the event.
I think adding an on/off switch and being able to optionally add expiration would be a wonderful thing. @gruntrebel and I are going to implement these over the weekend
Whatever time we choose as a cutoff point, we should stop accepting submissions and edits-- refuse
CollectController#creates/updates
, redirect the edit links to go to show, and have a "sorry, we're closed!" action or something.For short term fixes, we could have someone manually deploy a change or turn off the dynos or something at that time.
A neater, more sustainable fix would be to have a datetime setting on the event and make that change automatically.
The text was updated successfully, but these errors were encountered: