Looping through validation errors in view

Question

I'm using Laravel's form validation functionality and trying to work out how I can loop through the form errors in my view. At the moment, I'm successfully validating the form using the below code:

public function create()
{
    $validator = Validator::make(
        Input::all(),
        array(
            'username' => 'required|alpha_num|unique:users',
            'email' => 'email|unique:users',
            'password' => 'required|min:6',
            'passwordConf' => 'required|same:password'
        )
    );

    if ($validator->fails())
    {
        return Redirect::to('join')->withErrors($validator);
    }

    return View::make('user/join')->with();
}

The validator successfully validates the form and redirects to the join route if validation fails. Obviously, I'd also like to show the validation messages to the user. I have a master.blade.php layout file which all of my views extend, and in the layout I have the following code:

@if (Session::has('errors'))
    <div class="alert alert-danger">
        @foreach (Session::get('errors') as $error)
            Test<br />
        @endforeach
    </div>
@endif

This seems to half work. If there are validation errors, the alert div does show on the page, however no validation errors get output. That suggests that Session::has('errors') is returning true however I'm obviously not iterating through the validation errors correctly.

How do I iterate through the validation errors sent to the view via withErrors?

Joseph Silber · Accepted Answer · 2014-02-23 02:29:34Z

28

There's an automatic $errors variable passed to your view. You don't have to check the session directly.

@foreach ($errors->all() as $error)
    {{ $error }}<br/>
@endforeach

Here's a quote from the docs:

Notice that we do not have to explicitly bind the error messages to the view in our GET route. This is because Laravel will always check for errors in the session data, and automatically bind them to the view if they are available. 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. The $errors variable will be an instance of MessageBag.

edited Feb 23, 2014 at 2:29

answered Feb 23, 2014 at 2:24

Joseph Silber

221k59 gold badges369 silver badges292 bronze badges

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

2 Comments

John Dorean Over a year ago

Yeah, but not even "Test" shows up. If I change it to {{ $error }} I get the same result, the alert div shows up but not any error messages.

Dissident Rage Over a year ago

This is an insufficient answer because $errors contains a variety of structures to distinguish different kinds of errors.

Andrei · Accepted Answer · 2024-08-17 22:14:30Z

0

I don't know if this will help somebody with Laravel 11, but I had a similar problem with getting errors messages on route request data validation on form submit. So, as far as $errors in the view file has its inner structure, I did this to get errors messages:

@if($errors->any())
  <div class="errors">
    <ul>
      @foreach($errors->default->messages() as $error)
        <li>{{ $error[0] }}</li>
      @endforeach
    </ul>
  </div>
@endif

answered Aug 17, 2024 at 22:14

Andrei

11 bronze badge

Comments

Mohsen Khosroanjam · Accepted Answer · 2025-02-20 12:38:15Z

-3

It is also important to make sure that the php artisan vendor:publish --tag=laravel-errors command has already been done.

edited Feb 20 at 12:38

Mohsen Khosroanjam

6751 gold badge10 silver badges28 bronze badges

answered Feb 19 at 11:17

Uwem Frank

1

4 Comments

Nico Haase Feb 20 at 12:38

What do you mean by "also"? How does running this command ensure that form errors can be shown?

Uwem Frank Feb 23 at 6:35

I initially suggested php artisan vendor:publish --tag=laravel-errors thinking it might be relevant, but I now realize that this command only publishes Laravel's default error views (like 404 and 500 pages). It doesn’t affect validation errors in Blade views.

Uwem Frank Feb 23 at 6:36

In other not to mis-inform others. I'll be deleting my answer soon. Thank you

Nico Haase Feb 24 at 7:39

Please add all clarification to your answer by editing it

Collectives™ on Stack Overflow

Looping through validation errors in view

3 Answers 3

2 Comments

Comments

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related