Hey @almendron,
This notice about Jetpack’s translation loading being “triggered too early” is almost always a sign that another plugin or your theme is attempting to load Jetpack’s translations before WordPress is fully initialized. Jetpack itself generally follows best practices, but if another plugin or custom code interacts with Jetpack’s text domain too soon, it triggers this notice.
As a first line of troubleshooting, I recommend that you update all plugins that have new versions available, as well as your theme. This may resolve the issue without having to do anything else.
In case that doesn’t do the trick, I took a look at what plugins you might be using to see if anything stood out. There are reports that Broken Link Checker can trigger the “translation loading too early” warning if translations are loaded before the init action, so it might be worthwhile to temporarily deactivate that if issues persist after updating anything with an available update. I also noticed a few plugins that might be custom for your site, like Funciones and Buscador Avanzado. I’d try toggling those off as well, to see if the notice goes away.
To put your mind at ease, these kinds of notices in WordPress are generally for developers to identify code issues or compatibility, so they don’t typically affect the normal functioning, stability, or security of your site itself.
Let us know what you find after updating and trying to deactivate some of your plugins!
Cheers.
Thank you for the information. I will check it out.
Hi @almendron,
Sure thing – take your time to run some tests and let us know what you find out.
Take care for now 🙂
I have a question:
Why does the error message mention the Jetpack plugin?
Hello there, Sebastian here, I hope you are doing well.
It seems there is an issue with Jetpack functionality, often caused by a conflict with another plugin or theme. When you have the time, please follow the recommendations shared before:
- Update all plugins and your theme to the latest versions.
- If the issue persists, temporarily deactivate the Broken Link Checker plugin, as it may cause the translation loading warning.
- Try deactivating custom plugins, such as “Funciones” and “Buscador Avanzado,” to see if the notice disappears.
Remember, WordPress notices like this usually do not affect the regular operation, stability, or security of your site.
Please let us know how it goes.
Cheers,
First check: Broken Link Checker plugin dismissed
That issue was resolved in version 2.4.2:
= 2.4.2 =
- Fix: Patched a vulnerability issue.
- Fix: Notice about _load_textdomain_just_in_time.
Hi again @almendron,
Great, thanks for checking that and confirming the Broken Link Checker angle. That rules out the first possible source.
If the notice is still appearing, the next step would be to continue with the other plugins you have installed, especially the custom ones. Try deactivating them one by one to see if the message disappears.
If the issue persists even after checking the plugins, it’s also worth switching briefly to a default theme (like Twenty Twenty-Four) to see if the theme might be loading translations too early.
Let us know what you find and we can take it from there.
Theme discarded. Two blogs on the same server. Both with the same theme. The error does not occur on one of them.
I am going to check the plugins now.
Hi @almendron,
Since the theme is not causing the issue, please proceed with checking the plugins. Deactivate them one by one, especially the custom ones, to identify which might be triggering the notice.
Keep us posted!
Hey there, @almendron,
Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
I am continuing to investigate because I cannot find the source of the problem.
Hey @almendron,
Thanks for the follow-up – we’re sorry to hear you still have this problem.
Did you try to test the issue against the active plugins to see if that is caused by a conflict? If so, did you find anything useful for us to help you investigate? Anything you find can be useful, so please keep us posted.
Look forward to your reply 🙂
Hey there, @almendron,
Friendly check to see if you have updates to share, as we usually close inactive threads after a week. Thanks!
I’m still running checks. I’ve disabled all plugins except for 5. However, everything points to your plugin being the cause of the error.
Hello, Thanks for the update.
Since you’ve narrowed down the plugins to just five and the problem persists, I suggest checking if any of those five plugins are interacting with Jetpack unexpectedly. Try disabling them one by one to identify the culprit. Also, make sure all plugins and Jetpack are updated to their latest versions.
If the problem continues, please let us know so we can investigate further. Thanks!
