Big thank , you are right.

Hi,

A very useful question on this topic remains unanswered to me: "how i can identify which line produce this errror"?

I'm running Laravel 5 and had the same error message. Nothing in the stack trace or in the log files pointed me to root cause of the error. As I had a quite long legacy view (more than 2000 lines) it took me a long time to comment/uncomment each block until figure out which one was the guilty one.

Any ideas on how to get the view line shown in the error message or in the logs?

Chop the giant view up into many smaller partials and your debugging will be much easier.