Laurent

Hello,

First of all, thank you for NS Cloner — it’s a very solid plugin, and we’ve been using it extensively in a WordPress multisite context. Overall, the architecture and the cloning logic are really well thought out.

I’m reaching out regarding a debug notice that has become very visible since WordPress 6.7, especially on multisite installations with logging enabled.

Function _load_textdomain_just_in_time was called incorrectly.
Translation loading for the ns-cloner-site-copier domain was triggered too early.

I’ve seen your previous response mentioning that you plan to move things to the init hook, but that you were unable to reproduce the notice. After some in-depth debugging, I think I understand why it’s hard to replicate, and I wanted to share the findings.Context where the issue appears

• WordPress multisite
• NS Cloner activated at network level
• WP_DEBUG_LOG enabled
• Regular navigation in network admin

In this setup, the notice is emitted multiple times per page load (typically 2 to 4 times), which makes the debug log grow very quickly. Even though it’s not functionally blocking, it becomes quite noisy in production logs.What seems to trigger the notice

Leaving aside whether the plugin is intended to be network-only or also usable from sub-sites (I understand there may be Pro features relying on that), the key issue appears to be this:

• Some files required very early by ns-cloner.php (for example utility files) contain translation calls (__(), etc.) at global scope
• These files are loaded before init, and before WordPress considers translations “safe” to load
• On WP 6.7+, this causes WordPress to fall back to just-in-time translation loading, which now logs a notice

Because this happens very early, moving load_plugin_textdomain() to init alone does not fully prevent the notice.Why it’s easy to miss

• On single-site installs, the notice often doesn’t appear
• Without WP_DEBUG_LOG, it stays invisible
• On multisite, the same early code path may be executed more than once per request, amplifying the effect

Why this matters

Even though the notice is technically harmless, in a multisite / SaaS-like environment it can result in dozens of log entries per minute, simply from normal admin navigation.

At scale, this becomes a maintenance concern rather than a cosmetic one.

I’m sharing this mainly as feedback, not as a complaint — the plugin works well, but WP 6.7 has made these early translation patterns much more visible. It may be worth reviewing global-scope translation calls in early-loaded files to reduce log noise going forward.

On our side, this has also prompted us to reflect on whether a more infrastructure-driven cloning approach (WP-CLI + scripted batches) might be more appropriate long term, but that’s more an architectural consideration than a criticism of NS Cloner itself.

Thanks again for your work on the plugin, and feel free to reach out if you’d like more concrete pointers or examples.

Best regards,
Laurent