Do not enqueue scripts in an AJAX context about query-monitor

[johnbillion]

I would expect that most plugins that use the admin_enqueue_scripts hook enqueue scripts without checking for DOING_AJAX. Therefore the problem you're seeing with Query Monitor will also be seen in many other plugins that enqueue and localise scripts.

Unfortunately, this sounds like something your plugin needs to handle, rather than each individual plugin that enqueues scripts. What do you think?

[thefuxia]

Hm, yes, I could (and will probably) flush all existing registered scripts on $GLOBALS['wp_scripts']. But normally, plugins enqueue their scripts on the hook that is made for that: admin_enqueue_scripts, wp_enqueue_scripts, login_enqueue_scripts or customize_controls_enqueue_scripts. This is why QM was the only plugin adding its scripts to my plugin output.

Right now, QM enqueues its script on init. This is way too early, it doesn’t even wait for the spam blog check. It should use the proper hooks to avoid side effects.

[johnbillion]

Ah you're right. Not sure how I missed that one! I'll get it fixed in the next version.