SamNajian

Hello @mindykatzen,

Please feel free to upgrade to version 1.3.2 as it includes the fix for the notice mentioned above.

Happy new year to you too @mindykatzen, wish you successful, happy and fruitful 2025.

Please note that since these notices are simply only deprecation warnings, it’s fine to keep using the plugin until the patch is released, these warnings normally don’t pose any threats or issues.

Hope this helps.

Hello @8tracktapestore,

I’m sorry to hear about this trouble.

We need more information about your account the purchased labels to be able to proceed with your case, for this purpose please contact us using WooCommerce Support ( you can log in with your wordpress.com credentials), and we’ll be happy to assist you further.

Hello @mindykatzen,

Thanks for contacting us about this deprecation notice. It’s already fixed but not released because of end of year code freeze policy we practiced.

You can expect a release with this in the first half of Jan.

Hello @archfabricationandmachine,

Sorry to hear you’re experiencing this issue.

We’ve just released version 1.2.0, which specifically addresses caching problems. I recommend updating to the latest version and checking if the issue persists. Please let us know if the problem still occurs after the update.

Hello @tonymichalski , @vehix411,

Based on the other thread, it seems that the issue you’re experiencing is most likely related to caching. We’ve just released version 1.2.0, which specifically addresses caching problems. I recommend updating to the latest version and checking if the issue persists. Please let us know if the problem still occurs after the update.

Hello @ctheory11 ,

The fix for this issue is out with version 1.2.0, please upgrade and let us know if you experience the same issue again.

Hello @ctheory11,

Thanks for providing more context.

Apologies for not figuring out how to screenshot it!

The json you’ve provided is cut off at the end, but still I’m investigating to find a solution for it. We’ll keep you posted.

Hello @ctheory11,

Thanks for contacting us and reporting your issues, we appreciate your contribution.

As I’m trying to debug this issue, I was wondering about the value you get by pasting and runningWCShipping_Config.shippingLabelData.currentOrderLabels in your browser’s console? The result should look like this screenshot.

Please checkout this on how to Open Chrome DevTools or this for Firefox.

Hello @vehix411,

Thanks for getting back to us for your issues.

It takes sometimes 30 minutes for mw to print 1 label its been like this for a month.

Would you mind clearing a bit more what you’re facing and under what circumstances does this happen?

WooCommerce Shipping & Tax legacy settings and labels are being migrated to WooCommerce Shipping.

You may continue to use your website as usual. We will notify you once the migration process is complete.

I’m wondering how’s that going on? Do you see any progress or it’s completely stuck?

Also please report the WooCommerce and WooCommerce Shipping you’re using.

Providing more information can help us alot to fix this issue for you and potentially others as well.

Hello @plcexchange

Thanks for getting back to us with your question, we really appreciate your feedback.

Currently WooCommerce Shipping only supports creation and deletion of custom packages, so you can delete the package you don’t want and re-create it with the desired changes.

We are aware of this need and the good news is that we’ll ship the edit functionality in the coming releases.

• This reply was modified 5 months, 3 weeks ago by SamNajian.

Hello @morriemeritco,

Thanks for getting in touch and sorry to see this issue happening on your WordPress install, if you are using the MailPoet premium plugin, please make sure you are using the latest version.

Hope this helps.
Cheers!

I could fix this problem using some hints from this page,
all you need to do is :
1)go to wp-config.php and delete the blank lines at the end of the doc
2) go to functions.php in your theme’s folder and delete the blank lines at the end of the doc

Thanks goes to all who contributed