Not compatible with 6.7

Thanks Jacob, where are you seeing this message please? On every screen? In your logs?

When disable gutenberg is activated on every screen, in the query monitor error list

I’m seeing these error on every page view on my development machine where Query Monitor 3.16.4 is active. This appears to be related to this: https://make.www.ads-software.com/core/2024/10/21/i18n-improvements-6-7/ . That post, somewhat ironically, mentions Query Monitor as a tool to troubleshoot this :).

Hehe yes it’s a constant battle to get Query Monitor itself to behave because it has to hook into so many of the internals of WordPress.

• Is there a stack trace of that Doing It Wrong message?
• Does the message remain when all your plugins are deactivated and you’re using a default theme?

Hmm, this appears to be a little more complicated than I originally thought. I set up a brand new site, just WP 6.7 and Query Monitor. I set it to a non-default language and enabled WP_DEBUG, but got no errors.

The dev site I initially noticed this happening on had another plugin (Gravity Perks) active that caused the same error message. When I disabled that plugin, it also stopped the Query Monitor error being logged. So it could be that the error is somehow triggered by another plugin loading translations too early?

When the error does occur, I’m not getting a stack trace.

I noticed this: When a plugin uses __() prior to the init hook, it triggers an error that is captured by query monitor. Then: query montor tries to display the error – likely also prior to init – and uses __() itsself, causing the same type of error. Fortunately this errror reporting seems to be not recursive(!)

Thanks for the feedback both of you, I’ve managed to reproduce the problem. It is indeed triggered when another plugin attempts to load a translation too early. I’ll work on a fix.

Sounds great. Once again thanx for this exellent plugin that no developer should not install. Helped me to fix very many issues quickly!