fix "confirm" button in CFP (partly) #847
Merged
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
This fixes frab#817. If an event is accepted using "Accept, no mail" - a confirmation token is generated. The "confirm attendance" button on the CFP list now uses that token to evoke confirmation
saerdnaer
approved these changes
Sep 19, 2021
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 fixes #817.
If an event is accepted using "Accept, no mail" - a confirmation token is generated.
The "confirm attendance" button on the CFP list now uses that token to evoke confirmation
(I'm not sure if and how it worked previously)
I also don't have a solution for when the transistion from new -> unconfirmed is perfomed using direct editing of the event rather than by the "accept" button