69

When I want to register a user in my laravel project, the page always says

Undefined variable: errors (View: /var/www/resources/views/auth/register.blade.php)"

According to the Laravel documentation, $errors should always automatically be set:

So, it is important to note that an $errors variable will always be available in all of your views on every request, allowing you to conveniently assume the $errors variable is always defined and can be safely used.

I have this on on every view when I use:

@if (count($errors) > 0)
    <div class="alert alert-danger">
        <ul>
            @foreach ($errors->all() as $error)
                <li>{{ $error }}</li>
            @endforeach
        </ul>
    </div>
@endif

or any other way when I want to use the $errors variable.

Why is this? I never had this problem before.

Can someone help me please?

Improve this question
5
  • What version of Laravel? Specifically, in your composer.lock file, what version is it pulling? Commented Dec 24, 2015 at 14:14
  • Interesting. I haven't messed with 5.2 yet, but I can clearly see in the documentation what you are saying. Might be a bug in 5.2? laravel.com/docs/5.2/validation Commented Dec 24, 2015 at 14:25
  • Yes, Laravel 5.2 has bug. Many people have this same problem with Laravel 5.2 Commented Dec 24, 2015 at 17:00
  • check out this question: stackoverflow.com/questions/34420590/… Commented Dec 24, 2015 at 21:47
  • check out this answer stackoverflow.com/a/71614936/14344959 Commented Mar 25, 2022 at 9:48

10 Answers 10

Reset to default
132

You should make sure that in app/Http/Kernel.php in middlewareGroups property for web you have:

\Illuminate\View\Middleware\ShareErrorsFromSession::class,

in this array. Compare this with https://github.com/laravel/laravel/blob/master/app/Http/Kernel.php

EDIT

It seems you need to add 'middleware' => 'web' for route you are using or put \Illuminate\View\Middleware\ShareErrorsFromSession::class, into $middleware property array

or

Inside of the routes.php file try to create your routes within the following block

Route::group(['middleware' => ['web']], function () {
    //routes here
});

UPDATE FOR NEWER VERSIONS OF LARAVEL APPLICATION

Be aware that you might run into problems also in case you use web middleware twice. There was a change in Laravel application 5.2.27 (don't confuse it with Laravel framework you use at the moment - you might use Laravel framework for example 5.2.31 but have Laravel application in version 5.2.24) in which web middleware is applied automatically for all routes. So in case of problems, you should open your app/Providers/RouteServiceProvider.php file and verify its content.

You can compare it also here :

In case you have newer version (that applies web middleware automatically), you shouldn't use web middleware in routes.php anymore or you should modify your RouteServiceProvider method to not apply web group middleware. Otherwise if web middleware group is automatically applied in this provider and you use it also in routes.php you might get very unexpected results.

Improve this answer
Sign up to request clarification or add additional context in comments.

6 Comments

It's already in there... Copy-pasted the whole block to be sure, but it still doesn't work
Have you updated app from older Laravel release or you start new app from scratch in Laravel 5.2 ?
Started from scratch via scotchbox
Can you explain the first option a little bit more? Or where I should do this? I used your second option ('\illuminatte\...::class', into '$middleware') This solves the error, but now it gives me a new error: >Session store not set on request. Or what should I do to fix this one? Already thanks a lot!
@Anhinga Ok, so you should put also in $middleware also others from web group - EncryptCookies , AddQueuedCookiesToResponse , StartSession and VerifyCsrfToken (in same notation as in file Kernel I put link). At the moment you don't have session started so you are getting this error
|
20

I had this very same issue with Laravel 5.2.x.

Inside of the routes.php file try yo create your routes within the 

Route::group(['middleware' => ['web']], function () {
    //routes here
}

statement.

Improve this answer

1 Comment

Yeah that was the same issue with me too. I had created the home(/) route outside the web middleware
6

Also to be aware of: If you write tests and your view has $errors variable make sure you don't use WithoutMiddleware trait.

Improve this answer

Comments

4

I had similar problem and solved this one by adding routes into middleware property array as well,

BUT

it worked only after calling php artisan route:cache (clearing route cache) subsequently.

I hope some of you would find this useful.

Improve this answer

2 Comments

What? Cache needs to be cleared, in order middleware to working well.
Sorry, I don't know what I was thinking there.
3

I was seeing this error too and later realised I had used the WithoutMiddleware trait as a means to bypass authentication for this particular test, but it ended up removing the validation error binding too. So I had to stop using the trait to keep the views working.

Improve this answer

2 Comments

Thanks, this was my problem, too. Did you find a solution for testing stuff which has both the error variable and needs the WithoutMiddleware aswell?
@Fanmade Unfortunately I didn't. In my tests I just created a user and logged them in for each test. Fortunately laravel makes this possible with very little code so I don't mind it.
3

Your problem will be fixed by using this method. 

Route::group(['middleware' => ['web']], function () {
        //routes should go here
});

If this doesn't help you, just run the following artisan command in addition to the above code:

php artisan key:generate

I solved in this way while using 5.2.*

Improve this answer

Comments

3

Go to App\Http\Kernel.php file. Move all the things of $middlewareGroups properties to $middleware.

Improve this answer

Comments

2

count is not really realiable since it assumes the variable already exists. change the condition check to: @if($errors->has()) or just @if($errors)

Also if you are redirecting make sure to use this in your controller

return redirect()->back()->with('errors', $validator->messages());

EDIT: seen now that you are using L5.2 This may answer your question - you need to put your Routes in Route group.

Laravel 5.2 validation errors

Improve this answer

7 Comments

No, it checks for existance EDIT: if you are speaking of my controller suggestion, that part is only if for example - validation fails.
not really... where does it check for existance? $errors->has() ? assumes that $errors variables exists
If I'm not mistaken, has() method is boolean, so it will return 0 or 1 just like if you do if($errors)
To be more clear. Count needs to check inside of a variable $errors to find out how many items are there in array. has() method only return true or false without checking the variable. Hence, thats why it is method. I'm using my error handling in laravel like this since L4 and it works without a single problem aswell on my L5.1
I think you misanderstand something... $errors->has() means that a function called $has() is called on $errors. If $errors does not exists ( or is null or does not define has() function ) this will fail. Try it with $notexistant->has(). that will fail.
|
0 
protected $middleware = [              \Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
    \Social\Http\Middleware\EncryptCookies::class,
        \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
        \Illuminate\Session\Middleware\StartSession::class,
        \Illuminate\View\Middleware\ShareErrorsFromSession::class,
        \Social\Http\Middleware\VerifyCsrfToken::class,
];

/**
 * The application's route middleware groups.
 *
 * @var array
 */
protected $middlewareGroups = [
    'web' => [

    ],

    'api' => [
        'throttle:60,1',
    ],
];

/**
 * The application's route middleware.
 *
 * These middleware may be assigned to groups or used individually.

make your kernel look like this

Improve this answer

Comments

0

If you used group in Laravel 11 like this:

->withMiddleware(function (Middleware $middleware) {
    $middleware->group('web', [
        'throttle:100,1',
    ]);
    $middleware->group('api', [
        'throttle:100,1',
    ]);
})

this will OVERRIDE Laravel's default web and api middleware stack.

session management, CSRF protection, and sharing $errors with views (ShareErrorsFromSession), will no longer work unless explicitly included, because you OVERRIDDEN the default.

Instead of using group you should append the new elements you want to add to the default stack like this:

->withMiddleware(function (Middleware $middleware) {
    $middleware->web(append: [
        'throttle:100,1',
    ]);
    $middleware->api(append: [
        'throttle:100,1',
    ]);
})

So you don't have to add ShareErrorsFromSession by yourself, default already have it.

Now the $errors array will always be present in your blade files whether there are errors or not.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.