Hi Frédéric,
Thank you for reporting this and for sharing the error details.
This issue related to the load_textdomain_just_in_time notice has already been fixed and released in a recent update of the plugin.
If you’re not on the latest version yet, we recommend updating to the latest release and checking whether the notice has been resolved.
If the issue persists after updating, please share the following, and we’ll be happy to take a closer look.
- Plugin version
- WordPress version
- PHP version
You can share it securely through here.
Hello Frédéric,
It has been quite some time since our last communication. As we did not receive any follow-up questions from you, we will mark this thread as resolved.
Please open a new thread if you are still facing issues or have questions that you need us to answer.
I have version 3.3.9.1 (last). And this warning is still here sorry… Keep generating lines and lines in my debug.log !!
[13-Jan-2026 15:45:36 UTC] PHP Notice: The function _load_textdomain_just_in_time was called incorrectly. Loading the translation for the domain cookie-law-info was triggered too early. This usually indicates that code in the plugin or theme is executing too early. Translations should be loaded at the time of the init action or later.
Thank you.
Hi Frédéric,
Thank you for the update and for confirming the plugin version.
We’ve verified that version 3.3.9.1 includes the fix for the load_textdomain_just_in_time notice. In most recent cases, we’ve seen this warning persist when the WordPress core version is outdated or when there’s a compatibility mismatch between WordPress and the plugin.
Could you please update your WordPress installation to the latest stable version, and then check if the notice still appears?
Hi,
Thank you for investigating, but the issue is still here.
I have last wordpress version, caches flushed, reinstalled… WordPress debug.log is still growing…
[23-Jan-2026 08:40:40 UTC] PHP Notice: The function _load_textdomain_just_in_time was called incorrectly. Loading the translation for the domain cookie-law-info was triggered too early. This usually indicates that code in the plugin or theme is running too early. Translations should be loaded at the time of the init action or later. Please read Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/***/frequenceterre.com/wp-includes/functions.php on line 6131
WP config :
wp-core
version: 6.9
site_language: fr_FR
user_language: fr_FR
timezone: Europe/Paris
permalink: /%year%/%monthnum%/%day%/%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: production
user_count: 15
dotorg_communication: true
If you don’t fix this issue, I will have to find another cookie notice plugin. Sorry.
Hi Frédéric,
Thanks for the detailed follow-up. One important thing to check here is whether the site is still using the legacy version of the CookieYes plugin UI. The fix you’re referring to is fully available in the migrated (new UI) version, and sites that haven’t migrated may continue to see this notice even on the latest plugin version.
Please confirm whether your plugin has been migrated to the new UI. If not, you can upgrade by following the steps in our documentation here:
https://www.cookieyes.com/documentation/ui-migration/
After completing the migration, clear caches and recheck the debug log. If the warning still appears, we’ll be happy to investigate further.
Hello Frédéric,
It has been quite some time since our last communication. As we did not receive any response or follow-up questions from you, we will mark this thread as resolved.
Please open a new thread if you are still facing issues or have questions that you need us to answer.
