How to find exact error line in laravel 5.4 blade?

Question

I know laravel caches blade files, and when there is an error in blade, in version 5.3 error would be something like this :

Undefined offset: 0 (View:b5c0ef4df49585eadd7fc1fa15b2d8a03e8c3bdd.php) line: 47

Then I can go to cached files and find the exact line,

But in version 5.4 laravel reference the exact blade file(not cached file) but without a line number! Something like this :

Undefined offset: 0 (View: C:\wamp64\www\project\resources\views\events\partial\event_details_members.blade.php)
in Collection.php (line 1537)

Now how to find the error?

UPDATE

I know where the problem is, and how to fix that, But I want Laravel to tell me this automatically whether I have to look for it manually. what if the blade file is very big?

can you delete cache files from storage\framework\views and check or you can run php artisan clear — Vision Coderz, Sep 22 '17 at 10:08
@MayankPandeyz , here it is : `
{{ $m->translations[0]->role }}
`, I khow this is exactly the error — Ahmad Mobaraki, Sep 22 '17 at 10:10
ca you share full code of the blade.i guess this is because 0 key not there in that data — Vision Coderz, Sep 22 '17 at 10:11
@iCoders Yes I know that, and I can fix that, I want laravel to tell me this — Ahmad Mobaraki, Sep 22 '17 at 10:12

score 6 · Accepted Answer · answered Jan 27 '19 at 06:00

As of Laravel 5.7, the output shows stack frames on the left side and details of selected frame on right side. If you cruise through the stack, you'll find that one of the entries in there is the parsed version of your blade file (normally located near the (main) frame towards the bottom of the stack). Clicking this frame will take you to the exact line of the blade file that resulted in that exception.

Abilogos · Answer 2 · 2021-03-11T05:51:25.283

its not an easy way to find the error which raised in a cached view file.

but if your debug mode is off and you are going to find it out very quick,

I suggest this following steps:

I know this is not tidy.

1- find error in ./storage/laravel/log/today.log :

for example:

(b5c0ef4df49585eadd7fc1fa15b2d8a03e8c3bdd.php) (line : 47)

2- output the files content usng cat :

cat ./storage/framework/view/b5c0ef4df49585eadd7fc1fa15b2d8a03e8c3bdd.php

(file name from error log)

3- copy the content from terminal to an editor (from first line to the end)

4- you can find the buggy line.

score 0 · Answer 3 · answered Sep 22 '17 at 10:20

0

You can use Laravel Debugbar. This is easy to use. Follow below link you will get what you want.

https://github.com/barryvdh/laravel-debugbar

answered Sep 22 '17 at 10:20

Saroj

1,343
4
15
31

Thanks for mentioning. I have debugbar, It give's me the exact exception that laravel does, nothing more – Ahmad Mobaraki Sep 22 '17 at 10:23
So what you want then? – Saroj Sep 22 '17 at 10:24
1

Laravel exception or debugbar does not give me error line, See my update – Ahmad Mobaraki Sep 22 '17 at 10:29

How to find exact error line in laravel 5.4 blade?

3 Answers3