Laravel developer reference
Detailed Laravel, Livewire and PHP reference guides based on production debugging, security, deployment and application architecture work.
You changed a page and purged Cloudflare, but visitors still see the old version. Work through the browser, website cache and Cloudflare in the right order.
Read articleYour products are live, but Merchant Center says their landing pages are unavailable. Check the submitted links, find any Cloudflare blocks, and get Google to check the pages again.
Read articleYour landing page works, but Google Ads keeps rejecting it. Here is where to look in Cloudflare, which settings can block AdsBot, and how to get the ad reviewed once access is fixed.
Read articleStatamic caches every query string variation of a URL as a separate entry, so one advertising campaign can turn a 400 page site into 40,000 cache entries. Here is what Statamic is storing, how to audit your own cache, and how to fix it with allowed_query_strings and disallowed_query_strings.
Read articleA managed IT provider switched on a Cloudflare setting to block all bots from a client's site in July 2026. Googlebot was one of them, which took out organic search, Google Ads and every Merchant Centre listing at once. Here is how I traced it, and how to check your own setup.
Read articlePHP 8.5.10 is the latest stable release, and PHP 8.6 reaches general availability in November 2026. This guide covers every supported branch and its end-of-life date, the full 8.6 release schedule, how to find out which PHP version your site actually runs, why your server reports an older number than you expect, and how to upgrade without taking production down.
Read articleA Laravel 500 internal server error is a generic symptom with a specific cause hiding in your logs. This guide shows you how to find the real error first, then fix the usual suspects: permissions, missing APP_KEY, stale caches, Composer and PHP version issues, database failures, and web server misconfiguration.
Read articleThe "SQLSTATE[HY000] [2002] Connection refused" error means nothing was listening at the host and port Laravel tried to connect to. This guide covers all the common causes and how to fix them in Laravel 13, including localhost vs 127.0.0.1, Docker and Sail service names, custom ports, stale config caches, and CI pipelines.
Read articleThe "GET method is not supported for this route" error means the URL matched a route, but the HTTP method did not. This guide covers all the common causes and how to fix them in Laravel 13, including form method spoofing with @method, logout links, redirects that silently turn POST into GET, API verb mismatches, and stale route caches.
Read articleLivewire components run over HTTP, which means a lot of what feels like private server-side state is actually exposed to the browser. This guide covers how to secure a Livewire 4 application: the mental model, the protections Livewire gives you, and the practices that keep components safe, plus the lessons from the two real vulnerabilities that hit Livewire 3.
Read articleThe "Route [login] not defined" error in Laravel almost always means the auth middleware tried to redirect a guest to a login route that does not exist. This guide covers all the common causes and how to fix them in Laravel 13, including the redirectGuestsTo middleware method, starter kits, API-only apps, and Sanctum SPA authentication.
Read articleCORS errors in Laravel are almost always a config issue, not a code issue. This guide covers the common causes and how to fix them in Laravel 13, including allowed origins, credentials support, preflight requests, Sanctum SPA authentication, and wildcard subdomains.
Read articleBook a free strategy session with the senior people who scope and deliver the work. We will help clarify the problem, test assumptions and identify a practical next step—without turning the session into a generic sales call.
