Since updating WordPress, WooCommerce Shipping is now giving this error and I do not know how to fix it.
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-shipping 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. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/kq4dive73aob/public_html/wp-includes/functions.php on line 6121
The page I need help with: [log in to see the link]
Welcome to the WooCommerce Shipping Support forum, and thanks for reaching out. I understand how frustrating it can be to encounter this kind of error right after a WordPress update; let’s look into resolving this together.
That message is a warning related to how translations are being loaded, and it often comes up when a plugin runs certain code too early. To start, have you had a chance to check for any pending updates—especially for the WooCommerce Shipping plugin and any other plugins you may be using? Updating them might clear this up if the issue has already been addressed in a newer release.
If everything is up to date and the issue still shows, the next step would be to run a plugin conflict test. You can do this by deactivating all plugins except WooCommerce and WooCommerce Shipping, and then checking if the message disappears. From there, re-activate your other plugins one by one to see which one triggers the warning again.
If the warning still shows after the conflict test, it would be helpful to review your System Status Report. You can find this under WooCommerce > Status, then click Get system report and Copy for support. Please paste the report into a tool like https://quickforget.com or https://pastebin.com and share the link here—just be sure to increase the number of views or time before the link expires so we can access it.
Looking forward to your update, we’ll figure this out together!
I had checked for plugin conflicts before creating this post. None of them resolved the issue when deactivated. Here is the pastebin: https://pastebin.com/xzFwFm2x
Just to clarify, this isn’t a bug or actual issue, but rather a notice. It’s related to changes in how WordPress handles translation loading—a change that was introduced around October to December last year. This update is still being actively monitored, as outlined in this developer advisory: Translation Loading Changes in WordPress 6.7
To suppress the notice, you can follow the steps in the advisory by setting WP_DEBUG_DISPLAY to false in your wp-config.php file. This will hide the message on the frontend while you continue to monitor the situation.
Except that it IS a bug. The WooCommerce Shipping plugin has not been working as it should since that message appeared. There is no longer an option to create a shipping label nor the option to split shipments into two packages. This all stopped working at the same time as the code/warning appeared.
I understand you’re experiencing some issues with the plugin, but just to clarify — the notice you’re seeing isn’t a bug, but rather a warning that may have been triggered by an underlying issue.
To better understand what you’re encountering, could you please share a screenshot of the Shipping Label page, particularly where you’re not seeing the option to create a label?
Also, please go to WooCommerce > Status > Logs, and check for any entries related to fatal errors or WooCommerce Shipping. If you find any, kindly share the log via gist.github.com.
