187436627 registration only textbox - look at last #376
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
187460419 support delete event
This reverts commit ca55c9a.
Revert "Revert "187121499 enable default currency""
* main: Add the committee status to admin splashpage manually disable migration
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.
Pivotal Tracker Link
What this PR does:
This pull request implements snapcon issue #234. I added a message to registered users on a conferences splash page right above a conferences description. I also removed the warning message above the currency conversion admin page that says don't use because this has not been implemented. yet.
Include screenshots, videos, etc.
Who authored this PR?
@tiffanylamm
How should this PR be tested?
I wrote feature tests checking to make sure the message disappears for a non registered user and appeared for registered user.
Are there any complications to deploying this?
This requires a migration to add a new field registered_attendees_message to the conference model.
Checklist: