UPS Shipping using RESTful/OAuth API [Support Thread]

OK, this is bugging me. In the Developers Tool Kit, what shows for the database setting MODULE_SHIPPING_UPSOAUTH_HANDLING_APPLIES?

lat9:

OK, this is bugging me. In the Developers Tool Kit, what shows for the database setting MODULE_SHIPPING_UPSOAUTH_HANDLING_APPLIES?

I may be doing this wrong but when I enter that phrase I get no results found. Still using 1.2.0.

n8pbm:

I may be doing this wrong but when I enter that phrase I get no results found. Still using 1.2.0.
Thanks for that as it confirms my suspicion.

Let's try changing this section

                case '1.1.0':
                    $db->Execute(
                        'INSERT IGNORE INTO ' . TABLE_CONFIGURATION . "
                            (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, use_function, set_function, date_added)
                         VALUES
                            ('Fixed Handling Fee, Order or Box?', 'MODULE_SHIPPING_UPSOAUTH_HANDLING_APPLIES', 'Order', 'If the handling fee is a <em>fixed amount</em>, should it be applied once per order (the default) or for every box?', 6, 0, NULL, 'zen_cfg_select_option([\'Order\', \'Box\'], ', now())"
                    );

to read

                case '1.1.0':
                [B]case '1.2.0':
                case '1.2.1':[/B]
                    $db->Execute(
                        'INSERT IGNORE INTO ' . TABLE_CONFIGURATION . "
                            (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, use_function, set_function, date_added)
                         VALUES
                            ('Fixed Handling Fee, Order or Box?', 'MODULE_SHIPPING_UPSOAUTH_HANDLING_APPLIES', 'Order', 'If the handling fee is a <em>fixed amount</em>, should it be applied once per order (the default) or for every box?', 6, 0, NULL, 'zen_cfg_select_option([\'Order\', \'Box\'], ', now())"
                    );
                    break;                  //- END OF AUTOMATIC UPDATE CHECKS!

I think that worked. The error is gone and I am getting notified of the new upgrade. Testing the module I am getting shipping rates.

I do plan to upgrade but this was done with v1.2.0

Thank you

n8pbm:

I think that worked. The error is gone and I am getting notified of the new upgrade. Testing the module I am getting shipping rates.

I do plan to upgrade but this was done with v1.2.0

Thank you
Most excellent, thanks for helping with the debug! I'll get v1.2.2 released later today or in the morning.

My best guess is that early-adopters (i.e. those who started with v0.0.1) have gotten 'bitten' by this bug.

v1.2.2 of the shipping module is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2374

This release contains changes associated with GitHub issue #20, the 'naggy' message on upgrades.

lat9:

v1.2.2 of the shipping module is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2374

This release contains changes associated with GitHub issue #20, the 'naggy' message on upgrades.

I uninstalled 1.21, uploaded and overwrote all files. Enabled 1.22 and still get the message regarding missing keys or out of date. I'm around all week and weekend if you'd like to troubleshoot.

Also FYI adding the following code to line 94 removes the error:

case '1.2.2':

Same procedure you recommended in prior versions.

Thanks for posting this required change to includes/modules/shipping/upsoauth.php line 94, @Bubbadood.
Confirmed.

Perhaps an even easier solution would be to add a default case at this line. That way new versions wouldn't need to be added each time until there was another database change.

swguy:

Perhaps an even easier solution would be to add a default case at this line. That way new versions wouldn't need to be added each time until there was another database change.
The version checking process will be updated in the next release, using my more 'standard' version_check implementation.

We've come a long way since the old "you must remove and re-install" days!

Thanks for your hard work on this plugin.

Any plan to support UPS ground saver? It seems cheaper than the regular UPS ground.

https://blog.stamps.com/ups-ground-saver/

stamps.com users can create shipping labels for UPS ground saver now.

Here is more information:

https://support.pirateship.com/en/articles/8055600-ups-ground-saver-everything-you-need-to-know

Packages must be at least 4” high, 6” long, and .75” wide (4 x 6 x 0.75") and may not exceed 130” in length & girth combined
No one dimension can exceed 60” in length
Maximum weight is 70 lbs per package
Packages that weigh less than 1 lb will be subject to a minimum billable weight of 1 lb
Note: If you ship a package with UPS Ground Saver that exceeds any of the above weight and size restrictions, UPS will hit you with an "Over Maximum Limits" surcharge, which is $1,150

I've reviewed UPS' current documentation on their RESTful API and I don't see any reference to "Ground Saver" in the list of "Service Codes" returned.

Hi @lat9, thanks for your reply.

It seems ground saver cannot be found under ups website. Maybe it is still a pilot program now. Here are some developer information I found which are surepost related. I'm not sure if any difference between surepost and ground saver. Maybe UPS just rebranded surepost into ground saver.

https://www.ups.com/worldshiphelp/WSA/ENG/AppHelp/mergedProjects/CORE/Codes/UPS_Service_Codes_for_UPS_SurePost_Shipments.htm
https://stackoverflow.com/questions/27231907/ups-surepost-api

Here is the service codes for surepost (posted back in 2017):

92: UPS SurePost Less than 1LB
93: UPS SurePost 1LB or greater
94: UPS SurePost BPM
95: UPS SurePost Media Mail

At least, the example shipping label pirateship uses for ground saver is surepost label.
https://support.pirateship.com/en/articles/8055600-ups-ground-saver-everything-you-need-to-know

lat9:

Towards the bottom of the settings, there's

Quote Type
Quote for Residential or Commercial Delivery

I continue to wonder why the UPS Shipping module cannot use the shipping address to determine COM vs RES and bring back the appropriate rate. (WOrldship does this, so clearly UPS has the info.). It seems so logical - and can make a big difference (particularly for our relatively heavy items) in whether we are grossly over-charging for shipping (charging RES to a COM customer) or upside down (charging COM to a RES customer).

We were able to accomplish this via modifying the plugin, but having this capability as vanilla code seems obviously beneficial.

v1.3.0 of the UPS Oauth/Restful shipping module is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2374

This release contains changes associated with GitHub issue #22, enabling per-method handling fees.

Note: If you are upgrading from a previous version, pay particular attention to this Wiki article.

lat9:

v1.3.0 of the UPS Oauth/Restful shipping module is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2374

This release contains changes associated with GitHub issue #22, enabling per-method handling fees.

Note: If you are upgrading from a previous version, pay particular attention to this Wiki article.

United Parcel Service v1.3.0 - Missing Keys or Out of date you should reinstall! upsoauth

1.5.8a ; php 7.3.33

Upgraded from 1.2.0, I tried this

switch (MODULE_SHIPPING_UPSOAUTH_VERSION) {
case '0.0.1': //- Initial Beta release
case '1.0.0':
case '1.2.0':
case '1.2.2':
$db->Execute(

Which delivers rates, but still the error in admin United Parcel Service v1.3.0 - Missing Keys or Out of date you should reinstall!

lat9:

v1.3.0 of the UPS Oauth/Restful shipping module is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=2374

This release contains changes associated with GitHub issue #22, enabling per-method handling fees.

Note: If you are upgrading from a previous version, pay particular attention to this Wiki article.

I'm slow this morning LOL...

switch (MODULE_SHIPPING_UPSOAUTH_VERSION) {
                case '0.0.1':   //- Initial Beta release
                case '1.0.0':
                case '1.2.0':
                case '1.2.2':  
                case '1.3.0':                              
                      $db->Execute(

Fixed the nag as well.

v1.3.0 now uses my 'more standard' version_compare switch to determine whether an update is needed so those individual specific-version checks aren't needed.

What are you seeing for the handling fees?