Same here:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the translatepress-multilingual 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 /var/www/vhosts/MYDOMAIN.at/httpdocs/wp-includes/functions.php on line 6114
Plugin Support
Anca
(@ancavictoria)
Hello,
Thank you for reporting this.
Our dev team will investigate and fix this in on of the next plugin updates.
Kind regards,
Anca
Hi, have been looking for a temporary fix.
Apparently the main issue stems from an error in 6.7.
Waiting for 6.7.1 to resolve the issue.
https://core.trac.wordpress.org/ticket/62337
Hello @kio93 @jandal @strigga ,
Thank you for your patience!
We released the fix for this issue so please update TranslatePress to the latest version and see if everything is working correctly.
Let us know!
Kind Regards,
I still have the issue – downloaded the plugin from the site today (14-1-2025)
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cheerup 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/<website_dir>/public_html/blog/wp-includes/functions.php on line 6114
versions:
TranslatePress – Business V1.5.1
TranslatePress – Multilingual V2.9.3
Have the same issue for TranslatePress – Multilingual Version 2.9.5
Also noticed it adds infinitely “%3fv%3d9c049173fad5/” to the url until “ERR_TOO_MANY_REDIRECTS” thrown for the web page.
“Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cyr2lat 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.) inwp-includes/functions.php on line 6114”
Same issue now. I deactivated the plugin. When I reactivate TranslatePress, a fatal error occurs.
[08-May-2025 07:48:44 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the learndash-course-grid 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 /var/www/vhosts/mystery-solvers.com/httpdocs/wp-includes/functions.php on line 6121
[08-May-2025 07:48:44 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the learndash-notifications 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 /var/www/vhosts/mystery-solvers.com/httpdocs/wp-includes/functions.php on line 6121
[08-May-2025 07:48:44 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the learndash-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 /var/www/vhosts/mystery-solvers.com/httpdocs/wp-includes/functions.php on line 6121
etc
PS: while troubleshooting I reactivated the plugin, I now see a http error 500 instead of a fatal error.
Hello there,
The versions you mentioned are old since we have the TranslatePress-Multilingual 2.9.13.
Try to update to these versions and see if the problem persists.
Kind Regards,
I was using the latest version of the plugin. I went back to the previous by restoring a site back-up. After that I updated everything except TranslatePress and it is working again.
It is finally fixed after a long time and it had nothing to do with your plugin, apologies. Turns out the site’s database got corrupted when the hoster migrated the site for me from my former hoster. Issues with other things kept arising and i finally found out why.
Your plugin works like a charm now as it did before. I submitted a 5-star review.
Thank you
Problem persists!
WordPress:V6.81 TranslatePress – Multilingual v2.9.19 TranslatePress – Business v1.63
When i activated the above plugins, my store crashed, and error messages flooded in my debug.log, such as:
PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shoptimizer 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/wp-includes/functions.php on line 6121
And i have more than 30 languages, so more than 30 versions of the error message below in my debug.log, which made my site crashed.
10-Jul-2025 14:10:24 UTC] PHP Notice: Funktiota _load_textdomain_just_in_time kutsuttiin väärin. Käännöksen nimialueen kirki lataus käynnistettiin liian aikaisin. Tämä viittaa yleensä jostakin lisäosan tai teeman koodista, joka on käynnissä liian aikaisin. Käännökset tulee ladata toiminnolla init tai myöhemmin. Lisätietoja: Debugging in WordPress. (Tämä viesti lisättiin versioon 6.7.0.) in /home//wp-includes/functions.php on line 6121
Also the final message in the debug is like this, more than 100 pieces of this:
[10-Jul-2025 14:11:02 UTC] DeepL API request returned unexpected status code: 429
At this time, i have no choice but to disable these two plugins. Hope there’s a fix!
-
This reply was modified 9 months, 4 weeks ago by
martinxun03.