People searching “Laravel unique email Vue” hit this on the profile form. The user saves without changing the email, and Laravel says the email is taken. It is taken by the same row.
TL;DR
- Rule::unique()->ignore() lets the signed-in user keep their email.
- A plain unique rule fails on save.
- Do not ignore
$request->input('id')from the form.
The fix#
The Fortify guide owns login. This page is the update rule.
use Illuminate\Validation\Rule;
$validated = $request->validate([
'email' => [
'required',
'email',
'max:255',
Rule::unique('users', 'email')->ignore($request->user()->id),
],
]);
$request->user()->update(['email' => $validated['email']]);ignore() drops the current id from the uniqueness query. Pass the id, not the whole request.
On the Vue page, print form.errors.email under the email input. The message is the normal unique sentence. You do not need a second error format.
What to avoid#
Gotcha
Do not ignore $request->input('id') from the form. A visitor can change that hidden field and skip the unique check against someone else.
FAQ#
How do I ignore the current user on a unique email?
Rule::unique()->ignore() lets the signed-in user keep their email. A plain unique rule fails on save.
What goes wrong with Laravel unique email Vue?
Many developers hit this on the profile form. Do not ignore $request->input('id') from the form.
