Anhinga
Anhinga

Reputation: 823

Undefined variable: errors in Laravel

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?

Upvotes: 70

Views: 93251

Answers (10)

MarsPeople
MarsPeople

Reputation: 1824

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.

Upvotes: 0

tisuchi
tisuchi

Reputation: 954

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

Upvotes: 3

Asadullah Al Galib
Asadullah Al Galib

Reputation: 96

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.*

Upvotes: 3

Marcin Nabiałek
Marcin Nabiałek

Reputation: 111829

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.

Upvotes: 132

Krzysztof Boduch
Krzysztof Boduch

Reputation: 715

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

Upvotes: 6

Amit Rai
Amit Rai

Reputation: 1

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

Upvotes: 0

Tom11
Tom11

Reputation: 2519

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.

Upvotes: 4

Felipe Pe&#241;a
Felipe Pe&#241;a

Reputation: 2850

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.

Upvotes: 20

Nikush
Nikush

Reputation: 64

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.

Upvotes: 3

Vojko
Vojko

Reputation: 804

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

Upvotes: 2

Related Questions