The _load_textdomain_just_in_time function was called incorrectly

Hi @silasveta2012,

Thanks for raising this issue, It seems WP 6.7 started raising this issue.

I have a local setup in WP 6.7 but did not notice this error logged for the AIOS plugin.

I will create an internal ticket for this.

Regards

Hello,

this problem is kind of very urgent (level = Showstopper)!

Search for this in Google and you’ll already find hundrets of scanned websites – that’s a big security hole, because you offer the usage of wordpress, your plugins and maybe other details. In addition, the websites are ugly.

We had to deactivate this plugin – not fixed soon, we have to replace it.

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-wp-security-and-firewall 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 ***/wp-includes/functions.php on line 6114

Regards

Google: https://www.google.com/search?q=wordpress+plugin+%22all+in+one%22+Notice%3A+Function+_load_textdomain_just_in_time+was+called+incorrectly.+Translation+loading+for+the+all-in-one-wp-security-and-firewall+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.+%28This+message+was+added+in+version+6.7.0.%29+in+wp-includes%2Ffunctions.php+on+line+6114

Solved in other plugins: https://www.ads-software.com/support/topic/notice-function-_load_textdomain_just_in_time-was-called-incorrectly/

• This reply was modified 5 days, 7 hours ago by kimjo. Reason: Added links

kimjo

don’t panic, your link says that this is just a warning, and you definitely shouldn’t turn it off, they’ll fix it someday

No panic here – more annoyance. But I will not display errors on my website. no way.

That’s why i had to disable this plugin. I know, that this plugin is “free”, but your “they’ll fix it someday” displays the problem: Someday. Until that every visitor of my websites will see an error, think i am unprofessional, my website is not well managed and/or buggy, so they loose trust or are annoyed. Easy decision to disable the plugin directly.

This error shows, that this plugin is not ready for this WP version. Not a big problem, but it would have been helpful, when the plugin would be marked to the max WP version.

Hi @kimjo,

Yes, We suppose to work on this issue as high priority.

Still we can not replicate this issue. This issue is when a language is other than English is.

If you have Query monitor plugin installed and stack trace let us know.

The issue is the load_plugin_textdomain should be called in init not plugins_loaded we will fix this.

If the debug log enabled please disable it which might not show this notice.

define( 'WP_DEBUG', false );

Regards

• This reply was modified 4 days, 22 hours ago by hjogiupdraftplus.

I have this same problem (my WordPress is in Dutch).
I have installed and activated the Query Monitor and then the _load_textdomain_just_in_time function was called incorrectly warning went away.
When the Query Monitor was deactivated again the warning came back…

I had to disable define(‘WP_DEBUG_DISPLAY’, false); and define(‘WP_DEBUG’, false);

Temporary ok, but no solution – waiting for your fix. Thanks.

Hi @automaticrock,

You can disable the debug log as above reply.

@kimjo @silasveta2012

Also we have worked internally on the fix but still under testing and review.

I will keep you posted.

Regards

Hey @hjogiupdraftplus,

I am having the same problem with a German WordPress. Changing the language of WordPress-UI to English didn’t fixed the problem. The yoast-plugin had the same problem which was fixed in https://github.com/Yoast/wordpress-seo/releases/tag/23.9-RC1, might be worth a look?

Can you provide a beta-version of the fix to test?

Regards

Hi @rafaelmaeuer

Yes, once the fix is tested properly from our end,

I will provide the zip to install, The fix will be in next release and you do not have to wait.

Regards

Hello, just updated WP to 6.7.1, while errors persist in both the core and the plugin, maybe this will help fix

Linux server architecture 5.15.0-126-generic x86_64nginx/1.27.2 Web server softwarePHP version 8.2.26 (Supports 64-bit values)PHP SAPI fpm-fcgiPHP max input variables 4000PHP time limit 60PHP memory limit 128MPHP memory limit (only for administration screens) 256M

    _load_textdomain_just_in_time()
    wp-includes/l10n.php:1370
    get_translations_for_domain()
    wp-includes/l10n.php:1408
    translate()
    wp-includes/l10n.php:194
    __()
    wp-includes/l10n.php:306
    AIOWPSecurity_Audit_Events::setup_event_types()
    wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-audit-events.php:103
    AIOWPSecurity_Audit_Events::add_event_actions()
    wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-audit-events.php:33
    AIOWPSecurity_Audit_Event_Handler->__construct()
    wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-audit-event-handler.php:38
    AIOWPSecurity_Audit_Event_Handler::instance()
    wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-audit-event-handler.php:19
    AIO_WP_Security->plugins_loaded_handler()
    wp-content/plugins/all-in-one-wp-security-and-firewall/wp-security-core.php:438
    do_action('plugins_loaded')
    wp-includes/plugin.php:517

Hi @silasveta2012,

Thanks for the information. We have already identified this issue regarding AIOWPSecurity_Audit_Events::setup_event_types and fixed it still under testing.

Regards