Add subscription link support to notification email verification template #573
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.
Address #560, the backend part.
When
NOTIFY_EMAIL_SUBSCRIBE_URL
environment variable is provided, instead of embedding token to email it will be included as a link.With
SITE=http://127.0.0.1
andNOTIFY_EMAIL_SUBSCRIBE_URL=/subscribe?token=
, link will look likehttp://127.0.0.1/subscribe?token=<subscription_token>
. The token is not escaped and I'll escape it if it will be necessary when the frontend part will be written.After the frontend counterpart will be created,
NOTIFY_EMAIL_SUBSCRIBE_URL
default should be set to newly created URL location.That's how verification email looks like when subscribe_url is supplied: