Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.If you happen to be using a "Connection Address" (specified on admin/commerce/config/shipping/methods/usps/edit) of the USPS testing APIs:
http://testing.shippingapis.com/ShippingAPITest.dll
or
https://secure.shippingapis.com/ShippingAPITest.dll
You will receive this error in your Drupal log "API Authorization failure. RateV4 is not a valid API name for this protocol" and you will not see shipping rates displayed as part of the checkout process.
This is not directly an issue with commerce_usps. The underlying issue is that USPS's testing API does not support RateV4, but their production API does. I'm not sure it's worth having the commerce_usps module check if you're using the testing API and if so, revert to an older API version. This is more of a note in case anyone else is using the USPS testing API and runs in to this error. Just use the production API in the Connection Address:
http://production.shippingapis.com/ShippingAPI.dll
or
https://secure.shippingapis.com/ShippingAPI.dll
| Comment | File | Size | Author |
|---|
Comments
Comment #1
nodecode CreditAttribution: nodecode commentedI have to say this is a clear UI problem and I wholeheartedly agree there should be a "testing" mode or at least clear instructions on the homepage to explain that you must apply for full access to the production server before you can even start testing.
This could also be listed as a documentation issue.
Comment #2
andyg5000The patch in #1937062: Code clean up and prepare for a full release. addresses this from a UI perspective. The documentation needs help! Any takers?
Comment #3
MrPeanut CreditAttribution: MrPeanut commentedHey andyg5000, I think you could just rephrase the main module page and the settings page, like so:
Comment #4
andyg5000Thanks @MrPeanut!
I've updated the module page and the patch supplied in the issue above clears up any confusion on the admin form.
Comment #5
chase_hubbard CreditAttribution: chase_hubbard commentedEmailing them does not work, they just tell you over and over again that you must submit test requests before they will active it (see email quote below), which you cannot do because they do not allow RateV4 test requests, and RateV2 has been disabled.
I ended up having to call them, and at first I was told no, that I had to put forth some sort of test request, and then mentioned that I was trying to use RateV4, and she gave me access instantly.
Comment #6
andyg5000If you call them and say that you are using "3rd party software" (not developing your own), then they will move you into production. This is how it has been for years unless they've recently changed their policy.
Comment #7
MrPeanut CreditAttribution: MrPeanut commented@andyg5000 — For the record, I called about a month ago and told them I was using software that had already been tested and they immediately enabled production access. Email received the same response as #5 but calling and mentioning that worked instantly.
Comment #8
andyg5000