Issue with Translation Loading Due to Early Code Execution on WordPress Site

Hi, Same problem on my website.

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?really-simple-ssl?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.

• This reply was modified 1 week, 4 days ago by bertasz.

Hi @itrailer & @bertasz,

This notice was introduced in WordPress 6.7 and has to do with certain translations loading too early. An update of the plugin is therefore required in order to address this; but of course this will only address the notice that applies to really-simple-ssl specifically, the notice related to the wordpress-seo plugin would have to be addressed by it’s developer.

We will release an update to the plugin soon to fix this. I don’t think that it will be in time for the next upcoming release though, and it will most-likely be included in the update after that one.

Kind regards, Jarno

I do not think that is not a good enough response, are you saying that the problem is yours or are all the plugin authors wrong. It seems the problem has happened since your update so I think you should sort the issue out quickly for the next release

@clivesmith – The issue is occurring to hundreds of plugins and themes due to a change in the way 6.7 does language translations. I have just updated bbp style pack for exactly this reason. The original post showed this issue happening on their site for 2 plugins – really simple security and wordpress SEO – ie 2 entirely different plugins @jarnovos will obviously fix this for his plugin (just as I did for mine) but it is up to the authors of wordpress seo to fix the issue for their plugin.

• This reply was modified 1 week, 1 day ago by Robin W.

@robin-w – Hi Robin, thanks for the info, the problem is that not everyone is as quick as you at making the changes and some plugins may never get changed, it seems to me that 6.7 is a big change that maybe should have come with more warning.

Hi @clivesmith,

Thanks for your message. As mentioned by @robin-w, the notice was introduced in WordPress 6.7 and appears for any plugins that load translations prior to the init action (which in the case of the original poster concerned this plugin, really-simple-ssl but also another plugin wordpress-seo).

We will release an update soon to address the notice for this plugin; but authors of other plugins (such as wordpress-seo) would have to do the same for theirs.

Kind regards, Jarno

@robin-w and @jarnovos I am now confused, what I understood that many of the plugins are throwing this error because of WP 6.7 release and you are expecting the plugin developers to change their code?

If that is the case, then I am sorry, but I found this response strange. When you are releasing a new version would you not test with with at least the common plugins? For me, it looks that the bug is in WP code block only. Please look into it and resolve it.

Hi @amitblessed,

I’m not sure what you mean by this. The notice was added in WordPress 6.7 and it clearly mentions which plugin it relates to. In the case of the notice shared by the original poster of this thread, it mentions really-simple-ssl:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the really-simple-ssl domain was triggered too early.

An update for Really Simple Security will soon be released to fix it for this plugin. But we have no influence on the code of other plugins; we can only fix the notice for this plugin, Really Simple Security (really-simple-ssl).

Kind regards, Jarno

• This reply was modified 1 week ago by jarnovos.
• This reply was modified 1 week ago by jarnovos.

@amitblessed

The plugin developers have not followed the WP guidelines using the ‘init’ hook found in “How to Internationalize Your Plugin” and the updates must be done by plugin developers.

https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#loading-text-domain

@missveronicatv – if only it was that simple! Using functions such as get_template_directory and require_once( ABSPATH . ‘wp-admin/includes/plugin.php’ ); can now cause this issue under 6.7 !!

I contacted Astra theme ( has over 1 million installs) about this problem this was the reply I got

We understand you’re facing issues with the mails not sending and worried about the PHP notice. 

Function _load_textdomain_just_in_time was called incorrectly

This warning has been introduced after recent WordPress 6.7 update, and it is originated from WordPress itself but not Astra or any other theme. You can find this warning on several themes. The issues has been reported to WordPress for further fixes.

I cannot contact one of the other themes (Inspiry themes) without buying support again

Does not look like the theme people think it is their problem

• This reply was modified 1 week ago by Clivesmith.

Having ‘fixed it’ for my plugin (bbp style pack), I have since found that several things cause this ‘error’ to display that are not related to load_textdomain at all, and yes whilst I can change code to get round several of these, it is starting to look like a failure in 6.7 rather than inherrent bad coding in plugins!

@clivesmith – thanks for your update which supports this view !

It seems that people who are using woocommerce are having some big problems, https://developer.woocommerce.com/2024/11/11/developer-advisory-translation-loading-changes-in-wordpress-6-7/ see the comments

• This reply was modified 1 week ago by Clivesmith.

Just updated to 6.7.1, I hoped this might have sorted the issue but no still the same, this is madness

The release notes say

‘WordPress 6.7.1 is a fast-follow release featuring 16 bug fixes?throughout Core?and?the Block Editor?with a strict focus on bugs introduced in WordPress 6.7.’

The issue you reported only shows as an error message, unless you are saying that it is affecting functionality?

Error messages should not be enabled for live sites.

But I appreciate that it is frustrating, it caused me several hours of effort to track what was happening.