Back to Community

Resolving the WordPress 6.7 '_load_textdomain_just_in_time' Notice in Duplicator

34 threads Sep 10, 2025 PluginDuplicator

Content

With the release of WordPress 6.7, many users have encountered a new PHP notice related to translation loading. This notice frequently appears when using the Duplicator plugin and can fill up debug logs. While it's a notice and not a critical error, understanding and resolving it helps maintain a clean, efficient site. This guide explains the cause and provides the most effective solutions.

Understanding the Notice

The notice looks like this:

PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the duplicator domain was triggered too early... in .../wp-includes/functions.php on line 6114

This message was introduced in WordPress 6.7.0. It's not an error that breaks your site; it's a notice that acts as a developer warning. It indicates that code within a plugin or theme is attempting to load its translations before the WordPress core is fully ready to handle them. Translations should be loaded during or after the `init` action for proper execution.

Why This Happens with Duplicator

This notice appears because a part of the Duplicator plugin's code runs and triggers its translation functions too early in the WordPress loading sequence. The Duplicator team is aware of this issue, and it is expected to be addressed in a future plugin update. In the meantime, the following solutions can resolve or mitigate the notice.

Common Solutions

1. Wait for a Plugin Update

The most straightforward solution is to wait for the Duplicator team to release an official update that moves the translation loading to the correct hook. This is the ultimate fix and will resolve the notice without any action on your part.

2. Disable WP_DEBUG (For Production Sites)

If this notice is appearing on a live production site, it likely means your WP_DEBUG setting is enabled. For performance and security, this setting should be turned off on live sites. This will hide all debug notices, including this one.

To disable debugging, open your site's wp-config.php file and ensure the following line is set to false:

define( 'WP_DEBUG', false );

Note: This doesn't fix the underlying issue but simply hides the notice, which is acceptable for a live site where debug logging should not be active.

3. Check for Conflicting Plugins (Advanced)

In some cases, other plugins can interact and cause similar issues. As a general troubleshooting step, you can test for a conflict by temporarily switching to a default WordPress theme (like Twenty Twenty-Four) and disabling all other plugins except Duplicator. If the notice disappears, reactivate your plugins one by one to identify the culprit. This is a standard WordPress troubleshooting practice that can help isolate the source of many issues.

Conclusion

The _load_textdomain_just_in_time notice is a common sight after upgrading to WordPress 6.7. It is a harmless notification that the Duplicator team is working to resolve. For most users, the best course of action is to ensure WP_DEBUG is disabled on production sites and to keep the plugin updated to receive the official fix when it is released.

Related Support Threads Support