Filament intercepting regular user registration flow?
I'm building an admin panel to supplement a Laravel app. Users currently go through a regular login/registration flow using Breeze auth.
Now that I have added Filament, it seems to intercept a user registration so that, when the user clicks on the email verification link, it takes them to a 403 unauthorised error page - this is because they do not have permission to access the Filament admin panel (using the canAccessPanel method in the User model, only users with an admin role can access Filament, by design).
So I'm confused. I don't want Filament to interfere with regular users, but I don't see why this is happening. Can anbody help?
3 Replies
Did you add
->verifiesEmail() or something to the panel? Not sure whether that should interfere with other registrations thoughI have an existing (and until now working) user model that implements MustVerifyEmail. So users must click on the verification link sent by Breeze auth after registration. The problem now (after I have begun to implement FilamentUser in the User model) is that the verification email link seems to pass through Filament, which the user does not (and should not) have access to, so the user gets a 403 forbidden error in the middle of the verification flow.
i haven't added ->verifiesEmail() to the panel because i don't want filament to have anything to do with the user registration flow. and users will not access any filament panels.
hmmm... just testing this again, i seemed to go through registration ok this time...
Solution
Yup, please ignore the above - it seems to work ok now.