|
Kitka
|
November 28, 2024 at 11:22 pm
Does anyone know what this error means? It is a fresh site with no content. Activating the EE core plugin creates 3 errors at the top of the page:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-graphql 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 /home/kitkanet/public_html/yha/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the event_espresso 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 /home/kitkanet/public_html/yha/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the event_espresso 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 /home/kitkanet/public_html/yha/wp-includes/functions.php on line 6114
|
|
Tony
|
November 29, 2024 at 2:52 am
Hi there,
WordPress 6.7 changed how translations load and now also throws a ‘doing_it_wrong()’ notice (which is what you are seeing above) if translations load earlier than what WordPress expect.
The short answer as to why is if you run translations ‘too early’ before the WP_User has been loaded then your translations will use the site default language rather than the language set on your specific user account (because the account hasn’t loaded yet so only the ‘site language’ is known), its ‘doing_it_wrong()
The above notices aren’t technically errors, a notice is a way of saying ‘something isn’t right here, the code works but needs investigating’.
—
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-graphql domain was triggered too early.
This one is from a plugin we bundle into Event Espresso and we’ve created a ticket for them to fix this.
The other 2 are from our code, is that from just activating the plugin and then they instantly show? (Just trying to reproduce so I can find out where the ntoices are being thrown from)
|
