Tutorial on how to debug Laravel like a pro?

Open Network Tab with when you dealing with AJAX Requests, 500 means Server error and Method No Allow Exception is - let's say you have a GET route, when you send a POST request to it, you get this exception, and not only POST, PUT and DELETE and any other HTTP request - but not GET. And this exception causes that 500 error :)

console log all the data you send, then dd() data from the request, if everything is OK, move to next step, save, or delete, or whatever, good luck!

Don't forget about storage/logs/laravel.log

If you are on V5.7 (and it is quite easy to upgrade so why not) then there is something called a dump server available.

You run this as a command with php artisan dump-server

The command keeps running and if your application throws an error, it will be output in this console window instead of being sent to the client.

You can also use dump() in your code if you want to check progress or inspect variables at any point in your code.

I've recently started using Laravel Debugbar and it's been really helpful with debugging and optimizing queries.

@Sergiu77 dd() everything into console.log() is cool until it return the entire page and have no idea what the log is all about.

@Snapey Can Laravel be update from v5.5 without affecting my code?

@wilk_randall adding that package make me feel that everything bloated. I never put much effort into it.

Thats not something I can answer, it depends if you are using any changed features.

The upgrade instructions take you through it.

You will also need php 7.1