John Blackbourn

Sorry I missed this. This is indeed one of the main missing features, and I'm working toward allowing this via #483 which allows QM to show data from previous requests.

The `template_include` filter that ultimately populates this value is one of the more troublesome filters that QM hooks into. You'd be surprised at the great lengths some themes go to...

As mentioned on Twitter I had a branch at some point which overrode the global `$wp_scripts` and `$wp_styles` globals in order to instantiate a class which extended `WP_Scripts` and `WP_Styles`...

The short answer is no, unfortunately. This sounds like a useful thing to add though. I'll add it to my to-do list.

Thanks, the secondary database support isn't very widely used so I wouldn't be surprised if there are bugs there. I'll try to find some time to take a look!

Good suggestion. I've thought about this too but I think it would have to be opt-in from the Settings panel to avoid potentially clashing with other existing shortcuts.

I'm going to close this as it's not something I'm interested in spending time fixing myself, but feel free to open a PR if you find a good solution.

Thanks for the message. QM should already handle this here: https://github.com/johnbillion/query-monitor/blob/master/classes/Backtrace.php#L24 . It could well be that this has broken at some point though. I'll look into it.

Yeah documentation for the hooks in QM is on my todo list. You can use the `qm/dispatch/html` filter to disable all HTML output on a given page: ``` add_filter( 'qm/dispatch/html',...

This hasn't been requested before, but I can certainly see a use for it. This is very closely related to #173 and will be enabled by the same work.