Opened 2 months ago
Closed 2 months ago
#62541 closed defect (bug) (worksforme)
Function _load_textdomain_just_in_time was called incorrectly.
Reported by: | reteinformatica | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.7.1 |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
I have problems after upgrading to version 6.7. I had initially solved it, although sometimes the errors would come out but sporadically, by setting the backfront to English instead of Italian which is my language.
After the 6.7.1 update everything got worse, error after error on both the backfront and the site.
My site: https://todabe.it/
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr 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 /xxx/xxx/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the elementor-pro 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 /xxx/xxx/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpr-addons 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 /xxx/xxx/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpr-addons 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 /xxx/xxx/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpr-addons 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 /xxx/xxx/public_html/wp-includes/functions.php on line 6114
Warning: Cannot modify header information – headers already sent by (output started at /xxx/xxx/public_html/wp-includes/functions.php:6114) in /xxx/xxx/public_html/wp-admin/includes/misc.php on line 1438
Warning: Cannot modify header information – headers already sent by (output started at /xxx/xxx/public_html/wp-includes/functions.php:6114) in /xxx/xxx/public_html/wp-includes/functions.php on line 7137
Deprecated: Calling get_class() without arguments is deprecated in /xxx/xxx/public_html/wp-content/plugins/google-site-kit/third-party/google/apiclient/src/Http/REST.php on line 49
Warning: Cannot modify header information – headers already sent by (output started at /xxx/xxx/public_html/wp-includes/functions.php:6114) in /xxx/xxx/public_html/wp-admin/admin-header.php on line 9
Hi there and welcome to Trac!
As the messages clearly say, they are coming from specific plugins. This is a new change in 6.7 that reports if a plugin is loading translations too early. You can learn more about it at https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/
Most plugins have already started fixing their code. If not, you can point them to that articke.
You also shared another message, a deprecation warning originating from Site Kit. You‘d need to report that there.
None of these messages are from WordPress itself