[Bug] $errors->first('attribute') doesn't contain any value

[lembubintik]

At first it was working fine the validation errors was passed to the view. Ater updating the laravel framework errors are not showing.

from my controller

return Redirect::route('login')->withErrors($validator);

from my view

{{ $errors->first('password', '<p>:message</p>') }}

I can see that the error is there but it does not pass to the view

if ($validator->fails())
{
    echo $validator->errors()->first('email');exit();
}

[dberry37388]

I too am experiencing this issue. The MessageBag object when using withErrors() is coming back empty. with() also when combined with Redirect is giving the same result.

Forum post with further examples - http://forums.laravel.io/viewtopic.php?id=4694

[brunogaspar]

I'm having this same issue, it was working a few days ago, but now whenever i

return Redirect::to('somepage')->withErrors($validator);

I can't access the error messages, seems that the flash is not being set properly or something

Here is my controller method: http://paste.laravel.com/gan
And my view: http://paste.laravel.com/gao

[dberry37388]

I've got it traced back to the Illuminate\Session\Store finish method. It's storing it to flash and putting it in the $this->session['old']['errors'] like it should be and on the next request, you can pull it up using $app['session']->get('errors').

so this leads me to believe that where ever the View is adding the $errors var it's just not populating it. I'm trying to find where that is in the code base now. Just posted this update so if someone knows where the View is checking to see if the session has an errors entry and adds it, they can tell me where or check it themselves.

[brunogaspar]

@dberry37388 https://github.com/laravel/framework/blob/master/src/Illuminate/View/ViewServiceProvider.php#L128 ?

[dberry37388]

So it looks like for some reason the Session object at the point it is being loaded here has not been set yet and is pretty much empty. So when it is looking at $app['session']->has('errors'), at that point in time, it returns false. But if you check $app['session']->has('errors') later in the request, it returns true.

I'm using APC, but here is the session object at the point where sessionHasErrors is being called:

http://paste.laravel.com/gbI

and here it is later in the request. you can see that the session data is now there.

http://paste.laravel.com/gbO

[brunogaspar]

Hmmm yeah, i noticed that, so, something was changed somewhere, because i'm pretty sure it was working a few days earlier..

[dberry37388]

I'm not sure where to look from here, it's kind of like pissing in the wind for me... But hopefully that will help someone with a little more knowledge than myself.

[taylorotwell]

I worked with @dberry37388 on this and it seems to work fine on a fresh install. Can some of you others confirm. I can't recreate this.

[dberry37388]

It works fine, until I create a package using workbench and add that workbench's project to the config. My guess is I noticed that when you do the:

php artisan workbench --composer

and it updates and all, it add an Illuminate\Support to the vendor folder in the package directory. Maybe there is some sort of conflict going on there? I'm stabbing in the dark here.

[brunogaspar]

@taylorotwell Sorry, but it doesn't work on fresh installs, not for me anyway.

This is the code i tested.

Routes.php: http://paste.laravel.com/gdI
HomeController.php: http://paste.laravel.com/gdJ
Hello View: http://paste.laravel.com/gdL

To note that i didn't change anything else, or added new packages to composer.json, it simple doesn't work, and stopped worked, while in my current project using L4 it was working perfectly fine, so something seems to be "broken" somewhere :c

[taylorotwell]

@brunogaspar in your example you are never actually calling the validator. Call validator->fails() or something before passing it to withErrors. Your example works fine when I add that.

[brunogaspar]

@taylorotwell fair enough, forgot about it, it works indeed on fresh install.

But in my working project it doesnt, and it looks like it has something to do with the'Meido\Str\StrServiceProvider' from https://github.com/meido/str weird stuff.

Thanks!

[brunogaspar]

@taylorotwell So, i have looked at that package service provider, and it looks like the problem is with the boot method, more precisely this line https://github.com/meido/str/blob/master/src/Meido/Str/StrServiceProvider.php#L21

[alexwhitman]

I'm having the same problem but I'm not using the meido/str library.

If I dump $app['session']->has('errors') at https://github.com/laravel/framework/blob/master/src/Illuminate/View/ViewServiceProvider.php#L164 it returns false. If I dump Session::get('errors') in my controller then I get the MessageBag containing the errors. Dumping $errors in my view shows an empty array.