Notice in error log PHP

Resolved Fred17
(@f14m07)

1 year, 6 months ago

Since the last WP update I have this lines very often in my error PHP log file :

[15-Nov-2024 07:57:02 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>simple-history</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/mofr4003/public_html/wp-includes/functions.php on line 6114

[15-Nov-2024 07:57:02 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>simple-history</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/mofr4003/public_html/wp-includes/functions.php on line 6114

Viewing 15 replies - 1 through 15 (of 15 total)

Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

Thanks for the report. What version of Simple History do you have?

The usage of load_plugin_textdomain that I believe is what triggers this was removed in Simple History 4.10.0 that was released in January 2024 , so perhaps this is due to running an older version?

Thread Starter Fred17
(@f14m07)

1 year, 6 months ago

Hi,

I use the 5.1.0. The message is since WP 6.7 update

Thread Starter Fred17
(@f14m07)

1 year, 6 months ago

The last entries:

[15-Nov-2024 10:12:01 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>simple-history</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114 [15-Nov-2024 10:12:04 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>simple-history</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114 [15-Nov-2024 10:12:06 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>simple-history</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114 [15-Nov-2024 10:12:06 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the <code>simple-history</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /home/xxxx/public_html/wp-includes/functions.php on line 6114

Thread Starter Fred17
(@f14m07)

1 year, 6 months ago

when I desactive Simple History, no error logged. When I reactive, there are these errors.

Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

Unfortunately I can’t reproduce this myself. Could you provide info about your theme and what other plugins you have installed on your site?

Thread Starter Fred17
(@f14m07)

1 year, 6 months ago

The theme is Twenty Twenty-ThreeVersion: 1.6.

I used other plugins but as I said when I desactive Simple History, no error logged. When I reactive, there are these errors.

Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

Ok, thanks for the info.

While I can’t reproduce this myself (no notice warnings anywhere) I have seen the notice message on other sites now. If anyone else has the same problem please let me know your plugins and theme!

mirkoschubert
(@mirkoschubert)

1 year, 6 months ago

Hi, I can confirm those notices (and some warnings). Since the WordPress 6.7 update a lot of plugins have this notices as well as a “header already sent” warning on the login page, including Simple History. This seems to be a problem with recent i18n changes:
https://make.ww.wp.xz.cn/core/2024/10/21/i18n-improvements-6-7/
There are a lot of core tickets for this:
https://core.trac.ww.wp.xz.cn/search?q=_load_textdomain_just_in_time&noquickjump=1&changeset=on&ticket=on
Worst case it looks like this (random site):
https://deinballkleid.de/abendkleider-kaufen/koeln/

This is only appearing when debug mode is on, of course. But many users forget this setting when publishing their website or it’s still for testing in production.

Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

Thanks for the info @mirkoschubert

I am still unable to reproduce this on my local site so at the moment I don’t know what changes I should make to fix this :/.

I appreciate any help in creating a reproducible case!
mirkoschubert
(@mirkoschubert)

1 year, 6 months ago
Hi @eskapism, I just looked into it a little bit more. It seems that you load a translation in /inc/services/class-licences-settings-page.php on line 81 with the plugins_loaded hook, which is loaded before after_setup_theme and init.

Did you set the debug settings in the wp-config.php on true?
```
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', true);
```
Then you should be able to reproduce those notices. If you use a debug plugin such as Query Monitor, you should also see the errors there.
Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

@mirkoschubert Thank you for looking that up. I’m still confused why I don’t see any warning/notices. I do develop with both WP_DEBUG true and with Query Monitor running, but still no message (see screenshot). It must be something I’m missing.. 🤔

Simple History debug

Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

OMG I finally got the error! Of course I must have the language set to something else than English for translations to be loaded 🤦. Thanks for the help everyone, now I can fix the bug.

Plugin Author Pär Thernström
(@eskapism)

1 year, 6 months ago

Ok version 5.2.0 is out now with a fix for this notice. Let me know if it works for you!

mirkoschubert
(@mirkoschubert)

1 year, 6 months ago

@eskapism Of course, I didn’t think about that, because WordPress is in German for me every time (and in English as a user). I just updated one of my projects. Seems to work great 🙂

Thread Starter Fred17
(@f14m07)

1 year, 6 months ago

Thanks a lot for the quick fix

Viewing 15 replies - 1 through 15 (of 15 total)

The topic ‘Notice in error log PHP’ is closed to new replies.