MustVerifyEmail - it is not a trait

It must be an error... it is clearly an Interface. Just remove the use trait syntax inside the model.

Ah okay.

So there's a few steps it seems that are missing from the documentation and the Laracast video (at least in the way Laravel was installed in my project).

The User model needed this code:

<?php

namespace App;

use Illuminate\Auth\MustVerifyEmail;
use Illuminate\Notifications\Notifiable;
use Illuminate\Contracts\Auth\MustVerifyEmail as MustVerifyEmailContract;
use Illuminate\Foundation\Auth\User as Authenticatable;

class User extends Authenticatable implements MustVerifyEmailContract
{
    use MustVerifyEmail, Notifiable;

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'name', 'email', 'password',
    ];

    /**
     * The attributes that should be hidden for arrays.
     *
     * @var array
     */
    protected $hidden = [
        'password', 'remember_token',
    ];
}

Not sure why the documentation and the Laracast video show something different?

Because... updates???

Hmm most likely, but then surely now they already have outdated documentation and tutorial videos for their latest version?

Anyway I've got it working after being confused for a couple of hours :)

No worries...

Hmm most likely, but then surely now they already have outdated documentation and tutorial videos for their latest version?

Feel free to make a pull request and fix them: https://github.com/laravel/docs

Ah I wasn't aware you could do that. I will take a look, thanks.

@JeffreyWay need to know if the laracast video is wrong. He definately only adds implements mustVerifyEmail... no sign of a trait

Actually, the trait is pulled in by the Authenticatable (User model) class

vendor/laravel/framework/src/Illuminate/Foundation/Auth/User.php

class User extends Model implements
    AuthenticatableContract,
    AuthorizableContract,
    CanResetPasswordContract
{
    use Authenticatable, Authorizable, CanResetPassword, MustVerifyEmail;
}

So you should not have needed to add the trait.

I think you just confused contract and trait

Hi Snapey,

You know what? You're absolutely right I must have just been conflating the documentation and the video for some reason.

Thanks a lot

Laravel 5.7 docs example shows the trait included but it isn't required.

It was when 5.7.0 was released but I see the verification code has been in development over the past few days with changes in 5.7.1 and 5.7.2.

It is confusing as the docs say to start a new project using laravel new blog but as-of today this installs 5.7.2 which appears to be work in progress, and also doesn't match the 5.7 documentation.

So, what version should we be using to stay in-line with the documentation?

Hey guys, i am trying to use email verification on different model, not in users model by using this trait and it is not working atm. Can anyone suggest how to implement a similar feature but not on users model? You can view my question here:

Ok so i have a model named SiteEmail. Basically i have a model named Site and it can have multiple emails associated with it, which has to be verified by sending an email. I want to use the laravel email verification that ships with laravel which i have used on the user model. I have implemented the MustVerifyEmail interface on the SiteEmail model and it is using the Notifiable trait. The emails are being sent fine, but on clicking on the verify button, it says invalid signature.

class SiteEmail extends Model implements MustVerifyEmail { use Notifiable; protected $fillable = ['site_id', 'user_id', 'email', 'email_verified_at'];

    /**
    * Determine if the user has verified their email address.
    *
    * @return bool
    */
    public function hasVerifiedEmail()
    {
        return $this->email_verified_at != null;
    }

    /**
    * Mark the given user's email as verified.
    *
    * @return bool
    */
    public function markEmailAsVerified()
    {
        $this->update([
        'email_verified_at' => now(),
        ]);
    }

    /**
    * Send the email verification notification.
    *
    * @return void
    */
    public function sendEmailVerificationNotification()
    {
        $this->notify(new VerifyEmail);
    }

    /**
    * Get the email address that should be used for verification.
    *
    * @return string
    */
    public function getEmailForVerification()
    {
        return $this->email;
    }
}

How do i approach email verification on such models? It works fine on the User model, but i don't think this is the correct way to verify custom models. Any help is appreciated! Thanks!

PS: I think this might be happening because the signature generated is being tested against the user's email?

@pokhrelashok2 just roll your own