John Blackbourn

Is there something unusual about the directory structure of the files on your site? For example, are your plugins, themes, or wp-content directory in an unusual location or symlinked?

Okay this has been fixed in 1.9.1. Thanks for the reminder!

Thanks! I’ve already got a fix planned for this: https://github.com/johnbillion/user-switching/pull/143 . I’ll get a release out soon.

@paultgoodchild Can you share the code that triggers that fatal error please? (Or a cut down version of it if necessary.)

Thanks for the report.

Do you know when this error occurs? Is this something you are seeing in your PHP error log or can you reproduce the error by visiting a URL on your site?

Is there anything unusual about the database configuration on your site?

Not currently. Query Monitor does output HTTP headers with debugging info for some non-HTML responses, for example Ajax requests, but nothing for wp-sitemap.xml.

Thanks for the message. Yes, you can just deactivate the plugin when it’s not needed.

Query Monitor doesn’t affect the behaviour of the cache, it only reports what’s happening.

What’s the fatal error message?

This is a side effect of other plugins on your site that are triggering this error. Query Monitor itself only triggers the error when another plugin does.

I will of course get this fixed, but the underlying problem is that other plugins on your site are loading translations too early, which in turn causes Query Monitor to do the same when it attempts to log the error. The error message itself was newly introduced in WordPress 6.7. This is affecting a large number of plugins.

@nick7766 This is a side effect of other plugins on your site that are triggering this error. Query Monitor itself only triggers the error when another plugin does.

I will of course get this fixed, but the underlying problem is that other plugins on your site are loading translations too early, which in turn causes Query Monitor to do the same when it attempts to log the error. The error message itself was newly introduced in WordPress 6.7. This is affecting a large number of plugins.

Unfortunately I’m not able to test and ensure support for every plugin out there. Nothing fundamental has changed in User Switching for many years, so you might want to get in touch with the author of the dokan plugin to see if they can take a look.

Good luck!

This appears to be a side effect of another plugin on the site loading its translations too early, which ironically causes QM to load its translations too early when it catches the “doing it wrong” call.

Is there also another plugin triggering the same notice for its own translation textdomain?

Thanks for the report.

I fixed an instance of E_STRICT in the previous release but it looks like I missed one other. I’ll take a proper look next week.

Thanks for the message.

What problem is that confirmation causing? Adding force_switch_user=true is a good way to avoid it if it’s absolutely necessary.

What other actions and filters would you like?

Query Monitor essentially calls extension_loaded( 'redis' ) for its check (and does the same for several other object caching extensions). Whether or not the actual Redis connection is working is outside the scope of this check in Query Monitor, this is a convenience message more than anything. I don’t think it makes sense to extend its check beyond checking for the extension.