_load_textdomain_just_in_time Called Incorrectly.

Hello Mohammed Jamsheed KM,

Thank you for taking the time to report this issue.

Could you please confirm if this problem is occurring solely with WordPress 6.7.0-beta?
Looking forward to your response. ??

Best regards.

Hi?Zubair Zahid,

I’m currently not experiencing the error anymore. I’m using WooCommerce 9.4.0-beta.2 and WordPress 6.7-beta2-59195, and everything seems to be working fine now. It appears that the issue has been resolved with these updates.

Thank you for checking in!

Hi Zubair Zahid,

After further testing, I’m unfortunately encountering the error again, but this time it seems to be happening specifically when I visit a translated WooCommerce page.

I’m still using WooCommerce 9.4.0-beta.2 and WordPress 6.7-beta2-59195, but the issue seems tied to the translation aspect of WooCommerce. Could you please advise if there have been any related updates or if you need additional details to help diagnose the issue?

Thank you for your continued support!

Hey @jamsheedkm ,

Thanks for sharing the steps to reproduce the issue. I’ve tested this on my end and I’m unable to reproduce the issue when using WordPress 6.7-beta2 and WooCommerce 9.4 Beta 2.

Would you mind sharing a screenshot of the error as you’re seeing it on your end? Snipboard.io?can be used for easily sharing screenshots – please follow the instructions on that page, then paste the URL in this thread.

Additionally, please can you share the following:

• System Status Report:?you can find this via?WooCommerce?→?Status. Select?Get system report?and then?Download for Support. This will download a TXT file that has the contents of the SSR which you can then share with us here.
• Fatal Error Log:?Share a copy of any fatal error log found under?WooCommerce?→?Status?→?Logs

Cheers!

Hey,

Thanks for testing the issue. I believe you can reproduce it by visiting a translated WooCommerce page. The issue likely occurs because the load_plugin_textdomain function is being called too early, before the plugin is fully loaded.

I recommend using the init hook instead of the plugins_loaded hook for loading text domains. This aligns with WordPress 6.7 requirements, which specify that text domains should only be loaded on init or later.

You can refer to this line in the WordPress core: WordPress GitHub – l10n.php

At this stage, I don’t think it’s necessary to provide a screenshot, as the issue is likely related to the loading sequence of the text domain. If you’re still unable to reproduce the issue following this suggestion, I’ll be happy to share a screenshot as needed.

Thank you!

Hey @jamsheedkm ,

Thanks for clarifying! Since you’ve mentioned this happening with WooCommerce 9.4.0-beta.2 and WordPress 6.7-beta2-59195, can you try testing this with WordPress Beta version to 6.7-beta2-59226 and see if that resolves the issue on your end?

If the issue is still present, can you please report your findings, following the steps at?https://make.www.ads-software.com/core/handbook/testing/reporting-bugs/

Cheers!

Hi there,

I tested the issue with WooCommerce version 9.4.0-beta.2 and WordPress 6.7-beta3-59237, but the error is still occurring:

PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce 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 /Applications/MAMP/htdocs/support/wp-includes/functions.php on line 6099

The issue appears specifically on translated WooCommerce pages, but it does not occur when using the default English language.

I have already reported this in the WooCommerce GitHub issues, and we hope it will be addressed in the 9.4.0 release.

Thanks for your support!

Hey @jamsheedkm ,

Ah, awesome, thanks for letting us know! Since you’ve gone ahead and reported this on GitHub, any further communication regarding this will be provided there from the devs. ??

I’ll go ahead and close this thread then, but please feel free to create a new topic if you need any further help!

Cheers

I’ve updated to woocommerce 9.4.1 and wordpress 6.7 and this error is flooding my logs on every woocomerce pageload basically

Hi, I am having this very same issue so I was wondering if someone could possibly let me know how it was resolved so I might try and do the same? Thank you

Hi @sourcedstudio1 and @nirkon,

I understand your concerns about facing a similar issue with this.

However, to align with?forum best practices, please create a new topic so that we can address your issue(s) separately.

You can create a new thread here:?https://www.ads-software.com/support/plugin/woocommerce/#new-topic-0
Thanks for understanding!?

This does not seem to be specifically a plugin issue. I am experiencing the “_load_textdomain_just_in_time was called incorrectly” error with at least 1/4 of my plugins installed after upgrading to Rollins. Trying to “resolve” in a file like functions_extension.php using

add_action( ‘plugins_loaded’, ‘custom_load_exampleplugin_textdomain’, 10 ); function custom_exampleplugin_textdomain() {

load_plugin_textdomain( ‘exampleplugin’, false, dirname( plugin_basename( __FILE__ ) ) . ‘/languages’ ); }

did not resolve the issue. I understand, that WordPress is not fully initialised when trying to load translation file of the plugin?!

Hey! I’ve also having this issue, did you guys solved it?

Temp. Solution:

Check here: https://developer.woocommerce.com/2024/11/11/developer-advisory-translation-loading-changes-in-wordpress-6-7/

Add

add_filter( ‘doing_it_wrong_trigger_error’, ‘__return_false’ );

to functions.php or if you have one functions_extension.php or functions_child.php

This filter will make sure, that your debug.log does not get flooded by the error any longer.

Edit: This is only a temporary solution. The issue still persist, do not forget. So, either you hack the plugins yourself or wait for the developers to address the problem with plugin updates.

• This reply was modified 2 weeks, 1 day ago by mmeid72.

Hello, First you have to update all plugins before the new version of wordpress, then update wordpress.

There’s just an issue with updraft and securepress for me. Then, all the others plugins run well.

I had the same issue at the beginning…