UPS Shipping using RESTful/OAuth API [Support Thread]

[lat9]

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

[n8pbm]

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.

[lat9]

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':
                case '1.2.0':
                case '1.2.1':
                    $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!

[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

[lat9]

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.

[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.

[Bubbadood]

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.

[Bubbadood]

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

case '1.2.2':

Same procedure you recommended in prior versions.

[swguy]

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

[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.