People searching “Fortify email verification Vue” build a second verification controller. The Vue starter kit already has the pages. The Fortify guide is the login post. This page is the switch that actually sends the mail.
TL;DR
- The Vue starter kit already verifies email.
- The user model must implement MustVerifyEmail, and the resend form posts to Fortify.
- Do not replace it with a Vue route that reads
?id=and marks the user verified. - Do not log the verification URL.
The fix#
In config/fortify.php, the feature list includes email verification. The user model has to implement the contract or Fortify will not send:
use Illuminate\Contracts\Auth\MustVerifyEmail;
class User extends Authenticatable implements MustVerifyEmail
{
//
}Routes that require a verified user use the verified middleware. A guest is sent to login. A user who has not clicked the link is sent to the verification notice.
The resend button is a POST. The kit page already does this. If you are adding it to another page:
form.post("/email/verification-notification");The link in the email is signed. Do not replace it with a Vue route that reads ?id= and marks the user verified. That skips the hash Fortify checks.
What to avoid#
Gotcha
Do not log the verification URL. It signs the user in as verified when it is opened.
FAQ#
How do I verify email with Fortify and Vue?
The Vue starter kit already verifies email. The user model must implement MustVerifyEmail, and the resend form posts to Fortify.
What goes wrong with Fortify email verification Vue?
Many developers build a second verification controller. Do not replace it with a Vue route that reads ?id= and marks the user verified.
