Translation loading for the content-control 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.
While we’re testing this on our end, could you try removing the translation from lines 31 and 38 in wp-content/plugins/content-control/content-control.php to see if that resolves it for you?
@simbian For the record I run Query Monitor while developing, and have not once seen these or they would have been cleaned up. I run full WP_DEBUG, SCRIPT_DEBUG enabled. I was only able to replicate this on the WP 6.8-beta.
Not seeing any more after this one was fixed.
This reply was modified 11 months, 4 weeks ago by Daniel Iser.
After update to WordPress 6.8-RC1, I have the same message. This happend for many themes and plugins.
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf 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 C:\MAMP\htdocs\my-site\wp-includes\functions.php on line 6121
The previous message is about acf, but there’s many other affected textdomains.
Affected textdomains: js_composer, acf, gp-limit-submissions, happy-elementor-addons and others, including my own custom theme.
Viewing 6 replies - 1 through 6 (of 6 total)
The topic ‘Function _load_textdomain_just_in_time was called incorrectly’ is closed to new replies.