John Blackbourn

Thanks for the message.

When you switch between users with User Switching, you genuinely get logged in as that user, there’s no pretending or mocking, and no overriding or filtering of user data or role data. The behaviour is identical to if you logged in with that user’s username and password.

What this ultimately means is if you’re seeing stale role data then there’s likely a caching issue. Perhaps you’re reading the role from a user object that was instantiated prior to switching user? The wp_get_current_user() function and the current_user_can() function all work as expected after switching user.

Yeah a large number of PHP errors can eat up memory due to the size of the stack trace that’s collected alongside each one. Query Monitor version 4 reduces that memory usage considerably, but it’s still potentially unbounded.

The nuclear option is to disable error handling in QM completely:

define( 'QM_DISABLE_ERROR_HANDLER', true );

Not ideal, but it’ll allow you to use all the other panels in QM.

Short of changing the way QM transiently stores the data that it collects, there’s not really anything I can do about this. Any attempt to put a limit on the number of queries or errors that QM collects immediately makes it less useful when you inevitably need to see that information.

QM also allows you to hide errors from certain plugins or themes, but this doesn’t stop the data being collected, it just prevents the admin toolbar from showing a coloured notification. Perhaps I need to introduce a new option for completely bypassing the collection of errors from certain plugins and themes.

Plugin deactivation is covered here: https://wp-crontrol.com/docs/deactivation/

The reports about direct file access and missing nonces appear to be false positives. WP Crontrol has a pretty strict set of security and code scanning configuration, but I’ll double check to be sure.

Thanks, I’ll take a look at both of those issues.

A few people have been asking about a browser dev tools version of Query Monitor. This is now available for Chrome! Details here: https://querymonitor.com/wordpress-debugging/browser-extension/ .

You’ll need to ask your web host or Cloudflare to take a look. It’s not something that the WP Crontrol plugin can fix.

Good luck!

Have you been able to test this with Query Monitor version 4 yet? It’s generally less susceptible to the lag caused by a large DOM that affected prior versions.

I’ve been doing some testing with Classic Editor and WordPress 7.0 trunk and not been able to reproduce anything that lags or locks up the editor.