Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_load_textdomain_just_in_time was called <strong>incorrectly</strong> #919

Open
f14m07 opened this issue Nov 18, 2024 · 4 comments
Open

Comments

@f14m07
Copy link

f14m07 commented Nov 18, 2024

Hi,
I have this message in my php error log since the last WP 6.7 update.
To see this error your site must be in a foreign language and you must have debug mode.

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /Users/xxxx/Local Sites/clone-reve/app/public/wp-includes/functions.php on line 6114

This isn't the only plugin to have this problem.
You must be in debug mode and with a foreign lang site to reproduce this notice.
Could you update your code please ?

Thanks for all.

Have a nice day.

Frédéric

@johnbillion
Copy link
Owner

johnbillion commented Nov 18, 2024

Thanks for the report. I've already been looking into a fix for this. It's ironically caused by the "Doing it wrong" handler in Query Monitor which gets triggered when another plugin loads a translation too early.

@johnbillion johnbillion added this to the 3.17.0 milestone Nov 18, 2024
@f14m07
Copy link
Author

f14m07 commented Nov 18, 2024

It's true because having deactivated the other plugins that have the same error, I no longer get the query monitor error. Thanks for your quick response

@johnbillion
Copy link
Owner

@f14m07 Are you still seeing this problem with WordPress 6.7.1?

@johnbillion johnbillion removed this from the 3.17.0 milestone Nov 27, 2024
@f14m07
Copy link
Author

f14m07 commented Nov 27, 2024

No it's Ok Not new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants