Workshop check in #1692
Merged
Workshop check in #1692
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SamLR
force-pushed
the
workshop-check-in
branch
2 times, most recently
from
904c4af
to
b402fc9
Compare
This feels like it's not the right way to do it but converting event_tz to be a pendulum timezone causes other errors. This seems to work so ship it
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is pretty ugly and bare bones but workshop stewards can now get a list of all attendees for a workshop and either sign in all of their codes at once or an individual one.
The pages can be found by going to
/schedule/workshop-stewardand selecting the venuethen the workshop
then signing people in
To help reduce the number of giant lists of attendees about the place the list of attendees is time locked to the hour prior to the workshop and then its duration. The user also has to have signed up as a volunteer and done the 'workshop Steward' training.
If the timelock is in effect they see the following screen (otherwise they receive a 401)
The timelock can be ignored in
DEBUGmode by adding?time_locked=trueto the URL for testing purposes