Open
Overview of the issue
If you have updated WordPress to the new 6.7 version, you might have seen this notice:
Function _load_textdomain_just_in_time was called
- Since WP 6.7, translations should be loaded after WP init hook, you can read about this issue here: https://wordpress.org/support/topic/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called-3/
- Some plugins load the translation files earlier, and this causes the previous error.
- Note that the error indicates which plugin caused the issue:
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 /home/customer/www/xxx.com/public_html/wp-includes/functions.php on line 6114
For this example, notice that the issue comes from the WooCommerce domain; it is most likely in the WooCommerce plugin.
We fixed the issue in our last plugin updates:
- WPML Multilingual CMS 4.6.14.
- WPML String Translation 3.2.15.
Workaround
You should update WPML & WooCommerce plugins to their recent versions.
If you still experience this issue, it is most likely related to another Theme or Plugin;
WordPress 6.7.1 will most likely have a fix for this issue (see this – https://core.trac.wordpress.org/ticket/62337)
Hello,
I have these notices for 3 other plugins:
– Yoast SEO
– The Event Calendar
– Complianz – GDPR/CCPA Cookie Consent
Even with the last plugin updates
If a desactivate WMPL: no more notices
Thank’s for help
Best
Vince
Hello Vince,
While we wait for WordPress 6.7.1, other plugins has also released new versions which solve this issue. For example, yesterday Yoast SEO 23.9 also addressed this situation.
We recommend you to keep all your plugins updated.
Regards
Hi there!
Any idea why these new releases are not showing up yet in my WP plugins list as updates? Itś been almost a week since their release and I haven’t get any update notification there.
Thanks in advance,
N.
Hello Nacho,
If you can’t see the WPML update available, please go to Plugins > Add New and go to the Commercial tab.
There, click on the “Check for updates” button, updates should be available now.
I hope it helps.
https://wpml.org/es/faq/updating-wpml-manually/
Hi Andrés,
thanks for your reply. Yeah, I’ve noticed it right after I sent my inquiry and it’s already done. Now everything looks fine.
I’m glad it helped.
Hi,
I have updated everything and I confirm that there are no dubug error anymore after the update. However string translation is not working yet in my case. In particular, I have translated strings related to divi template builder (e.g. domain: page-builder-shortcode-strings-5048).
Translation are visible in In WPML > string translation . However they are not showing up on the frontend.
Please help to fix
please discard my previous comment because I preferred open a ticket for this issue where I could upload images
Hello there,
Yes, it sounds like an specific case. It will be better to start a chat in our assistance channel to investigate it better.
Hi,
Unfortunately, updating to WordPress 6.7.1 did not resolve this issue in my case.
The translation from the native language to English is still not working.
Errors (“Function _load_textdomain_just_in_time”) related to the following plugins were found in the debug.log file:
– Gravity Perks
– Rank Math
– Rank Math Pro
For now, I have restored a full backup and will wait for a more stable solution.
Best regards,
Kalevi
Thank you for your report, Kalevi. We will keep this para updated once we have news.
I have this problem to
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the sitepress 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.
/htdocs/wp-includes/functions.php on line 6114
Hello Andreas,
This issue is still open as WP 6.7.1 didn’t provide a complete solution.
We will keep this page updated once we have news.