Debugging is the secret art of the experienced developer. The ability to inspect stack traces, rifle through response objects, and dump data to the screen is often the quickest way to get yourself unstuck and back on track. Here are some tools Statamic provides to help you debug.

Ignition Debug Screens

Ignition is an included Laravel package for debugging exceptions. It provides a clean and organized stack trace, code snippets, information about the request, and even the ability to share the error message with others.

To enable Ignition, set APP_DEBUG=true in your .env file.

Ignition error screen showing a typo in a collection tag.
This is Ignition. Isn't it pretty for an error screen?

Statamic will try to detect why you're receiving a specific exception and provide a solution for the problem along with a link to the most relevant documentation if possible. It's like Clippy, but 80% less annoying.

Debug Bar

The debug bar is a convenient way to explore many of the things happening in any given page request. You can see data Statamic is fetching, which views are being rendered, information on the current route, available variables, user's session, request data, and more.

Debug bar showing available variables
The debug bar is like X-Ray vision into many of Statamic's inner workings.

Benchmarking Response Times

You can see all of the major operations performed on a given page request in the Timeline tab, which can help with fine-tuning and performance optimization.

Debug bar the timeline
Slow tags or operations are candidates for caching or indexing tweaks.

Exploring Data

Any variables defined in a blueprint will be shown as a Value object in the Variables tab. They can be expanded to see their "raw" original data, as well what fieldtype they're managed by, and their augmented value.

How to Enable the Debug Bar

You need to require the package with Composer.

composer require --dev barryvdh/laravel-debugbar

And then enable it in your .env file:


The debug bar injects JavaScript into the page and adds significant overhead server-side work to each request. Make sure to turn it off when you're testing your site's performance!

Dump Modifier

When working in Antlers templates, you can slap the dump modifier onto any variable to explore its contents. Here's an example.

- Goo Goo Dolls
- Oasis
- Third Eye Blind
- Creed
- Hanson
- The Offspring
{{ bands | dump }}
// Dumped output
array:6 [
"good" => array:3 [],
"bad" => array:3 []


Statamic uses Laravel's logging handling system to log messages and errors to file, debug service, or even Slack. The default behavior logs these messages to files stored in storage/logs. Each day gets its own separate file so it can feel special (and make it easier to find what you're looking for).

Learn more about configuring other logging channels on the Laravel docs.

Viewing Logs in the Debug Bar

You can enable logs in the Debug Bar in its config file. If you haven't already published the config, you can do from the command line:

php artisan vendor:publish --provider="Barryvdh\Debugbar\ServiceProvider"

And then enable the "Logs" collector in your new config/debugbar.php config file.

'collectors' => [
'laravel' => true, // Laravel version and environment
'events' => true, // All events fired
'default_request' => true, // Regular or special Symfony request logger
'logs' => true, // Add the latest log messages
'files' => false, // Show the included files
'config' => false, // Display config settings

Laravel Telescope

Statamic supports Laravel Telescope, an elegant debug assistant for the Laravel framework. It's most useful when you're building addons or doing custom Laravel things outside the normal Statamic site scope.

Follow along with Laravel's documentation and you'll (probably) be up and running in no time.

Laravel Telescope showing nothing particularly interesting
Laravel Telescope in action. But just barely.
Docs feedback

Submit improvements, related content, or suggestions through Github.

Betterify this page →