UPS Shipping using RESTful/OAuth API [Support Thread]

[lat9]

ZC 158 w/ php 8.2

After upgrading to 1.4.0, admin page keeps saying: "NOTE: A NEW VERSION OF THIS PLUGIN IS AVAILABLE. [Details]"
The storefront can't get the correct quote.

The debug log:

    "response": {
        "errors": [
            {
                "code": "111580",
                "message": "Missing or Invalid account number for Payment Details."

Rolling back to 1.3.8 and works well

I've corrected the version number in the Zen Cart plugins (I'd submitted with a leading 'v').

For that error message, would you enable the shipping module's debug and create the log with that error. Then send it (possible zipped) via PM.

A screenshot of your UPS settings would help, too.

[lat9]

I've corrected the version number in the Zen Cart plugins (I'd submitted with a leading 'v').

For that error message, would you enable the shipping module's debug and create the log with that error. Then send it (possible zipped) via PM.

A screenshot of your UPS settings would help, too.

The UPS API v2409 is much more strict than the initial v1 (no surprises there). In @siliconbug's case, the site's setup requires use of a Shipper Number that's not associated with the site's API credentials. While UPS REST API v1 provided quotes with a nagging warning message, v2409 returns a hard error with no quotes.

I've seen another case of the API's hardening. If the Origin Postcode doesn't match the origin country/state/city, v1 would still give quotes (with no message) while v2409 returns a hard error with no quotes.

[njcyx]

Hi @lat9, is there a way we can still use new ups plug-in (v1.4.0) but with old UPS API (v1) instead of new API (v2409)?

[lat9]

Hi @lat9, is there a way we can still use new ups plug-in (v1.4.0) but with old UPS API (v1) instead of new API (v2409)?

That might work, but you'd be on your own if it doesn't.

[lat9]

That might work, but you'd be on your own if it doesn't.

... and might I ask: Why do you want to go back to the v1 API (which is already deprecated by UPS)?

[njcyx]

... and might I ask: Why do you want to go back to the v1 API (which is already deprecated by UPS)?

Hi @lat9, I saw the recent discussion (posted by @siliconbug), saying new API is more strict than the previous API. It looks like to me that, under some special cases I can still get a quote with V1 API but error with new API.

I haven't tried new API yet and hopefully it still works on my case. But if it doesn't work well, I have to go back to the V1 api (since my old plug-in is working fine).

[lat9]

Hi @lat9, I saw the recent discussion (posted by @siliconbug), saying new API is more strict than the previous API. It looks like to me that, under some special cases I can still get a quote with V1 API but error with new API.

I haven't tried new API yet and hopefully it still works on my case. But if it doesn't work well, I have to go back to the V1 api (since my old plug-in is working fine).

@siliconbug's case is a pretty special one. The only issue I've found with clients updates is that the city/state/zipcode/country must match with v2409; one client had moved to a location nearby ... but it turned out to be a different "official" city for the updated zipcode.

[njcyx]

Hi @lat9, I just made the new plug-in/API work. My case is the same as @siliconbug' case. Our UPS account was hacked before so a new UPS account was assigned. I haven't added the new UPS acct number to our developer account. I only put the new UPS acct in zen cart settings. I can still get a shipping quote today when using the previous API, but no quote when using the new API.

I checked our developer acct today, there is no UPS acct number in my app (the previous hacked one could be deleted by UPS already). Anyway, I added the new, valid UPS account to my app and I can get a shipping quote now using the new plug-in & API.

[njcyx]

I just noticed an issue (v1.4.0). After I updated the module, every time when I entered Admin--Modules--Shipping--UPS, I can see a notice on the top "The UPS RESTful/OAuth shipping module was automatically updated to v1.4.0'.

I did some tests and I changed the line 166 back to the previous version and this top notice doesn't show up any more...

$messageStack->add_session(sprintf(MODULE_SHIPPING_UPSOAUTH_UPDATED, $this->moduleVersion), 'success');

to

$messageStack->add(sprintf(MODULE_SHIPPING_UPSOAUTH_UPDATED, $this->moduleVersion), 'success');

zen cart 2.1.0. php 8.2

[lat9]

I just noticed an issue (v1.4.0). After I updated the module, every time when I entered Admin--Modules--Shipping--UPS, I can see a notice on the top "The UPS RESTful/OAuth shipping module was automatically updated to v1.4.0'.

I did some tests and I changed the line 166 back to the previous version and this top notice doesn't show up any more...

$messageStack->add_session(sprintf(MODULE_SHIPPING_UPSOAUTH_UPDATED, $this->moduleVersion), 'success');

to

$messageStack->add(sprintf(MODULE_SHIPPING_UPSOAUTH_UPDATED, $this->moduleVersion), 'success');

zen cart 2.1.0. php 8.2

Yep, that was previously reported. I've got a correction staged here for the 1.4.1 release: https://github.com/lat9/upsoauth/issues/56