VerifyEmail should not be called on the server. #26
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
|
Tnx! |
splendido
added a commit
that referenced
this pull request
Jan 8, 2016
Accounts.verifyEmail should not be called on the server.
splendido
changed the title
|
I can confirm that the reset password link works fine for me. I can't easily test the enrolment email on my current project. |
|
Ok, fine, they share the same logic... |
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.
When using FlowRouter 3 with SSR support the routes are also executed on the server, however
Accounts.verifyEmail()(which is executed when visiting theatVerifyEmailroute) is only available on the client and caused a server error. This PR fixes that.