Minor fixes to sponsorship packet stuff #16
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.
Looking to redeploy this as we begin to ramp up for our next hackathon, I realize I never submitted these fixes upstream, so I'm doing that now.
Firstly, it seems there was code added to
shared/packet.py
to handle getting the packet file path, but it wasn't used when attaching the packet to the email.Second, I set a default value for the location of the sponsorship packet in
website/static
so that I didn't have to set this when I was just getting the packet from a URL. This allows for easier first-time configuration, but also leaves the current level of configurability if desired.