Fixing the 'Translation Loaded Too Early' Notice in Broken Link Checker

If you've recently updated to WordPress 6.7 and use the Broken Link Checker plugin, you may have encountered a new notice in your error logs. This article explains what this notice means and what you can do about it.

The Problem: A Notice About Early Translation Loading

The notice looks like this:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the broken-link-checker 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.

This is a deprecation notice introduced in WordPress 6.7. It indicates that the Broken Link Checker plugin is attempting to load its translation files at a point in the WordPress loading process that is now considered too early.

Why This Happens

This notice is triggered by the plugin's code. The 'Broken Link Checker' team has confirmed they are aware of the issue and their developers are actively working on a resolution. The problem is on their end, not yours. The notice itself is a warning and typically does not break your website's functionality, though it can clutter error logs.

What You Can Do

Since this is a code-level issue within the plugin, the ultimate fix will come from the plugin developers in a future update. In the meantime, here are your options:

1. Wait for an Official Update: The most straightforward solution is to wait for the 'Broken Link Checker' team to release a patched version of the plugin. They are actively working on a fix.
2. Suppress the Notice (Temporary Measure): If the notices are filling your logs and causing concern, you can temporarily suppress deprecation notices by adding the following line to your site's wp-config.php file. Note: This is a general fix for hiding notices and should be used with caution.

   define( 'WP_DISABLE_FATAL_ERROR_HANDLING', false );

   Always remember to make a backup of your site before editing core files.
3. Check Your Translations: While unrelated to this specific error, some users have reported incomplete translations for the plugin. Ensure your site language is set correctly in Settings > General and check the Dashboard > Updates page in WordPress to install any available translation updates. This can improve the overall plugin experience.

For the most current status on this issue, you can monitor the plugin's official support forums on WordPress.org for any announcements regarding an update.