psychjay

Perfect, I’ll keep an eye on the feature stack of the new plugin as development continues. We will plan to migrate after the holiday season with our internal tech support team.

Thanks!

Thanks @doublezed2

Regarding UPS, you can continue using the same account over WooCommerce shipping for UPS-negotiated rates. It is explained in this?documentation.

Just for clarification so there is no room for misunderstanding on our side. Is this explanation talking about the new WooCommerce Shipping plugin? The linked documentation is under the WooCommerce Shipping & Tax subsection. Just trying to make sure we are on the same page.

WooCommerce Shipping / Documentation / **WooCommerce Shipping & Tax** / WooCommerce Shipping Guide / Using Your Own UPS Account in WooCommerce Shipping

Thanks!

Thanks for the answers on the other post I made!

Thanks for the response, this will help ensure we don’t have disruption to an upcoming increase in shipping volume over the next couple of months starting in October.

As for UPS, I don’t recall any documentation that we were in the beta, but it looks like we are a part of it based on the link in your response. What we have does line up with those instructions. We have had this plugin since it was called WooCommerce Services I believe and have had our UPS Carrier Account linked for years.

I was reading the developer advisory blog, checking on what the issue was causing the need to update to ver. 8.9.3 . As the issue is the “Order Attribution” feature deployed in January, you may want to try deactivating it in WooCommerce Settings/Advanced/Features, and unchecking “Order Attribution” to see if that helps.

I also see people were creating tickets about it before the security vulnerability was patched, impacting website speeds as a ton of extra scripts were being deployed on every webpage. While they improved the performance of the feature, the patch may have set that back as it is a critical security resolution over performance.

This may not be the full issue of the latest patch but it may help a bit in specific cases.

Thanks a bunch and my review has been upgraded as a result. Thanks for listening to the feedback and resolving the issue.

This seem to happen with WooCommerce Ver 3.1.0 and WordPress Ver 4.8 both installed. Ver 1.1.2 says compatible with WordPress 4.7.5, has it been tested with WP 4.8. Perhaps this a WordPress conflict and not WooCommerce? We did also have to roll back to 1.1 that fixed the issue.