Repository navigation
First release, for Pollora v13.35.3 (composer require --dev pollora/debugbar). It puts Pollora and WordPress in Laravel Debugbar, with the aim of making Query Monitor unnecessary in a Pollora project.
Tabs
- Pollora: what answered the request (
Route::wp(), the template hierarchy and its Blade view, a Laravel route), versions, discovery, modules, theme, async actions, constants and drop-ins - Doctor:
pollora:doctor's web checks, run on demand - WP Request: rewrite rule, query vars, queried object, main query, conditionals, template hierarchy; the admin screen in wp-admin; sites and site switches on a multisite
- WP Queries:
$wpdbqueries with time, backtrace, rows, errors, duplicates, slow ones, grouped by component - WP Hooks, and WP Hook timings (opt-in): actions that fired, callbacks registered by Pollora, and the slowest callbacks by their own time
- WP HTTP, WP Cache, WP Capabilities, WP Blocks, WP Assets, WP Languages, and WordPress's phases on the Timeline
Requests
- REST and admin-ajax calls are stored and listed in the bar; a
wp_redirect()keeps both requests - The bar shows in wp-admin, without Laravel's route, views and session tabs; no second bar inside iframes (Site Editor canvas, Customizer)
Extending
- WordPress plugins:
pollora/debugbar/register,pollora/debugbar/message,start/stop; Query Monitor'sqm/*actions keep working - Packages: extend
Pollora\Debugbar\Collectoror add aSectionProvider
Documentation: https://pollora.dev/advanced/debugging/