laravel-systematic-debugging

Start with root cause investigation: read the full error message, check storage/logs/laravel.log, and reproduce the issue in Tinker. Then form a single hypothesis, create a failing test case, apply one fix, and verify the test passes.

Enable Model::preventLazyLoading() in non-production environments to throw exceptions on lazy loading. Then identify the offending relationship and add eager loading with with('relation') to the query, verifying the query count drops.

Laravel Telescope provides visibility into requests, queries, jobs, events, and exceptions. Tinker lets you test hypotheses interactively, and DB::enableQueryLog() or DB::listen reveals the actual SQL and bindings being executed.

Laravel blocks attributes not listed in the model's $fillable array to prevent mass assignment vulnerabilities. Add the missing field to $fillable, then verify with a test that the record saves with the expected attribute values.

Stop after three failed fix attempts. Repeated failures where each fix reveals new coupling or creates new symptoms indicate an architectural problem, so question whether the Laravel pattern itself is correct before continuing.