#1 - The text, instead of variable names, now appears in the plugin correctly.
#2 - The 0.5oz decal with dimensions of L3.25in x W1.25in x 0.1in is still not yielding any results. The debug file just says
USPS 2: No shipping services available for the shipping address provided.
09.17.25 19:19:01
USPS 2: No shipping services available for the shipping address provided.
09.17.25 19:27:06
USPS 2: No shipping services available for the shipping address provided.
The old USPS plugin and usps.com itself both provide me with the same rates.
#3 - With NONSTANDARD vs MACHINEABLE, at least with Priority & Ground Advantage that we use, the results vary by weight/height/dimension, which will yield different results.
For instance, we have a book that is 9oz, 11 x 9 x 0.5 inches, and if ordered by itself, will only show results if I use MACHINEABLE. However, it provided the incorrect rate for Priority Mail ($34.35 vs. $13.30). It displays no results under 'NONSTANDARD' in the cart, but the debug output does show results coming back in an array.
In the debug array, it lists USPS Ground Advantage Machinable Single-piece for the correct amount ($9.50), but it isn't being displayed because I believe the processingCategory is MACHINABLE in the results.
And, if I switch to a different product that is 8lbs, 42 x 1.25 x 1.325 inches, ordered by itself, MACHINEABLE results in nothing. It requires using NONSTANDARD to get correct results for Priority Mail and Ground Advantage.
If both of these products are in the cart, the NONSTANDARD works, but the MACHINEABLE does not. There is a minimum that is not being met with NONSTANDARD, which would normally be met. Sometimes, a product's dimensions by themselves are not indicative of the actual shipping container.
The processingCategory being submitted doesn't seem to limit the results returned by USPS, and my guess is the plugin is doing the filtering.
This might explain why USPS.com itself and the old plugin provide results (with or without dimension) when the new one doesn't, despite returning hits in the array. I'm wondering if the plugin shouldn't be filtering in some cases.