Background of the issue:
I am trying to clean up some log entries that may be causing issues on my site. Link to a page where the issue can be seen: hidden link
Symptoms:
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the breadcrumb-navxt 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. I installed the latest version of String Translation because I read about a very similar issue and I thought that the update would fix it but not really. I still have those messages flooding my debug logs.
Questions:
How can I stop these debug log entries from appearing?
Is there a way to ensure translations are loaded at the correct time?
I will try to answer the question before assigning the ticket to one of my colleagues.
This is a known issue introduced by WordPress update to version 6.7.
Many plugs might be affected and you need to make sure that you update all plug-ins that you use because this is something that the plug-in developers need to address.
For our side, we've already fixed that issue by updating the WPML string translation plug into version 3.2.16.
We released an erratum regarding this issue that you can check here:
Hello There!
I hope you're doing well. Sorry for the delay in responding due to the weekend.
I understand your concern. Recently, WordPress has updated how it handles translations. These changes were introduced in the WordPress core, and plugins that previously implemented translation mechanisms using the older approach now need to adapt to these new updates in WordPress to ensure their translations load correctly.
In WPML, we have made the necessary changes and released an update. It's great to hear that you've updated the plugin to the latest version. As a result, you will no longer see any notices or warnings related to `_load_textdomain_just_in_time` from WPML or its addons.
However, if you still encounter that warning from any other plugin, you should reach out to the author or support team. They must update their plugin and adopt the new WordPress approach to resolve the warning. Most plugin developers are already aware of this change, so they will likely implement the necessary updates to ensure their plugin works correctly with the latest WordPress standards.
If the warning appears for a specific plugin, it indicates that the plugin has a translation issue, and its translations will not work correctly. While this does have a functional impact, it should not cause anything to break on the site.
I hope you can understand. Feel free to let me know if you have any other queries or concerns. I'll be happy to help.
Best regards,
Prosenjit
The topic ‘[Closed] Some incorrect translation timing causing tons of debug log entries’ is closed to new replies.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
