When something on a WordPress site behaves strangely, the question is usually \"which plugin is doing this?\". Hooktrail answers it for any page you open.<\/p>\n\n
Switch it on for yourself, open a page, and choose Hooktrail<\/strong> in the admin bar. A panel opens at the bottom of the page.<\/p>\n\n Every action and filter that fired, in order, grouped under WordPress's loading stages. Each row shows when the hook first fired, how many times it ran, how long its first run took, and coloured tags for every plugin or theme with a callback on it. Click a row to see each callback, its priority and the exact file and line where it is defined.<\/p>\n\n A chart of hook run times: each bar is a hook's first run, hooks fired inside it sit below it, and the slowest hooks are listed at the top. Click any bar to jump to that hook.<\/p>\n\n Every plugin, theme and WordPress core with the hooks it used on this page, and the hooks where more than one plugin or theme attaches a callback, listed in the order they run.<\/p>\n\n Pick a filter such as Every database query, with the hook that was running and the plugin or theme file, line and function that made it. Queries are totalled per plugin and repeated queries are grouped.<\/p>\n\n The theme template used for the page, the theme files loaded, and every script and stylesheet printed, with its size and the plugin, theme or external host that added it.<\/p>\n\n A short list of things worth a closer look: PHP warnings and notices with the plugin and hook that caused them, plugins on the same filter at the same priority, callbacks at extreme priorities, callbacks removed while the page loaded, repeated queries and slow hooks.<\/p>\n\n Callbacks registered on hooks that did not run on this page, grouped by plugin.<\/p>\n\n AJAX and REST API requests you made while recording (for example saves in the block editor), which never show a page of their own. Open any of them to see its full map.<\/p>\n\n Load two saved maps (for example before and after activating or updating a plugin) and see hooks, callbacks, priorities and assets that changed.<\/p>\n\n Only for you, and only while recording is on. Hooktrail listens to every hook, query and PHP warning during your page views, which adds some time to each of your requests. Visitors and other users are not affected.<\/p><\/dd>\n Recording starts when Hooktrail itself loads. Hooks, queries and warnings from before that, such as while must-use plugins and earlier plugins load, are not included. Callbacks those plugins add to later hooks are still shown. Filters that run before Callbacks: PHP Reflection gives the file and line where each callback is defined. Queries and warnings: the call stack shows the plugin or theme file that made the call. Files are matched against the plugins folder, the must-use plugins folder, the active theme and WordPress core.<\/p><\/dd>\n When a hook first runs, Hooktrail adds a callback at the very last priority, so it runs after every other callback on that hook and records the elapsed time. The time includes everything that ran inside the hook. The extra callback removes itself straight away.<\/p><\/dd>\n No. While tracing, each callback on that filter is wrapped so its input and output can be recorded; the wrapped callback receives the same arguments and its result is passed on unchanged. Only filters you choose are traced, only for your account, and only while recording is on.<\/p><\/dd>\nTimeline<\/h4>\n\n
Flame<\/h4>\n\n
By plugin and Shared hooks<\/h4>\n\n
Trace<\/h4>\n\n
the_content<\/code> or document_title_parts<\/code>, reload, and see its value before and after every single callback, with the changed text highlighted. You see exactly which plugin changed what.<\/p>\n\nQueries<\/h4>\n\n
Assets<\/h4>\n\n
Issues<\/h4>\n\n
Not fired<\/h4>\n\n
Background<\/h4>\n\n
Compare<\/h4>\n\n
Also<\/h4>\n\n
\n
WP-CLI<\/h4>\n\n
\n
wp hooktrail record <url> [--output=<file>]<\/code> records a page on this site as a logged-out visitor sees it.<\/li>\nwp hooktrail compare <a.json> <b.json> [--fail-on-change]<\/code> compares two maps; with --fail-on-change<\/code> it exits with status 1 when they differ, for deploy checks.<\/li>\nwp hooktrail hooks <plugin-folder> [--format=table|json|csv|markdown]<\/code> lists the hooks a plugin offers.<\/li>\n<\/ul>\n\nSafe to leave installed<\/h4>\n\n
\n
\n
\n
Does it slow my site down?<\/h3><\/dt>\n
Why are some early hooks missing?<\/h3><\/dt>\n
init<\/code> cannot be traced.<\/p><\/dd>\nHow does it know which plugin a callback, query or warning belongs to?<\/h3><\/dt>\n
How are hook durations measured?<\/h3><\/dt>\n
Does tracing a filter change my site?<\/h3><\/dt>\n