“_load_textdomain_just_in_time” notice flooding debug logs

Hi,

Are you working on a fix for the _load_textdomain_just_in_time notice caused by early textdomain loading? It’s spamming our debug logs, and since we need debug enabled on dev sites, a proper solution or workaround would be really helpful.

Thanks!

Hi Calin,

thanks for looking into this. A few additional details from our end:

1. We’ve used about ten different plugins that triggered the same “\_load\_textdomain\_just\_in\_time was called too early” notice, and they’ve all released fixes since WP 6.7 (November 12, 2024). The only one still spamming our logs is td-cloud-library.

2. To prove it’s definitely td-cloud-library, we spun up a fresh install with only the Newspaper theme plus tagDiv Composer and td-cloud-library active. With WP\_DEBUG (and/or WP\_DEBUG\_LOG) enabled, the notice appears—and disabling td-cloud-library alone removes it. Steps to reproduce:

* Install Newspaper theme + tagDiv Composer + tagDiv Cloud Library
* Add to wp-config.php:

`
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_DISPLAY’, true);
define(‘WP_DEBUG_LOG’, true);
`
* Visit any page and watch the notice flood the debug log.

3. We hunted down why that notice won’t go away under WP 6.7+. Here’s what we tried:

* Searched every PHP file in td-cloud-library for load\_plugin\_textdomain(…) calls—none exist.
* Made a small must-use plugin that removes WP’s JIT filters on “plugins\_loaded” and force-loads the text domain on init. But it still fails because WP 6.7+ attaches _load_textdomain_just_in_time so early that any __(…, 'td-cloud-library') call in the plugin’s global scope immediately triggers the notice—before our MU-plugin runs.
* In other words, as soon as the first translation function fires (e.g. __('…', 'td-cloud-library')), WP already tried and threw the warning.

What needs to happen: All translation function calls (__(), _e(), esc_html__(), etc.) in td-cloud-library must be moved out of the global scope so they don’t run before load_plugin_textdomain('td-cloud-library', …) fires on or after init. Until every translation call is wrapped in a callback (or otherwise deferred until after the domain is registered), that notice will keep spamming logs.

Hope this helps pinpoint the fix. Cheers!