Workshop listed - question on WRFs #1741
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
Templates changed: 1. Details templates for all 3 WRFs 2. Email reponses for users for all 3 WRFs 3. Email notifications for admins for all 3 WRFs
fmichonneau
approved these changes
Nov 6, 2020
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 PR fixes #1718 by introducing a new field
workshop_listedon all three WRFs:WorkshopRequest,WorkshopInquiryandSelfOrganisedSubmission.The new field looks like this:
The answer will affect
public_statusfield on Event during "Accept & create a new event": if selected "yes", "public" will be used, and if selected "no" then "private" will be used.