UPS XML: Support Thread

lat9:

I've just submitted v1.7.7 of UPS XML for the Zen Cart moderators' review; I'll post back when it's available for download.

 This release contains changes associated with the following GitHub issues:

#19: Correct PHP notices generated.
#20: Display "New version available" only from admin's Modules->Shipping
#21: Correct "Next Day Air Early" quotes not being returned.
#22: Restructure distribution.
#23: Sort quotes returned by cost.
Now available for download: https://www.zen-cart.com/downloads.php?do=file&id=126

5 updates in 5 months? Glad to have the responsiveness but is a bit onerous. Is it possible to wait and do one that covers all the bugs, er, upgrades? Although if one of these updates could determine the RES vs COM address status and bring back the appropriate rates, that would make the patch time entirely worthwhile.

Cindy, thanks for your support of this module and aggressive fixing of issues as they are discovered. The project is lucky to have you.

apollowilcox:

5 updates in 5 months? Glad to have the responsiveness but is a bit onerous. Is it possible to wait and do one that covers all the bugs, er, upgrades? Although if one of these updates could determine the RES vs COM address status and bring back the appropriate rates, that would make the patch time entirely worthwhile.
swguy:

Cindy, thanks for your support of this module and aggressive fixing of issues as they are discovered. The project is lucky to have you.

what swguy said.

appollowilcox, i would suggest you wait and do your updates as needed. just because lat9 keeps this complex add-on up-to-date is no reason for you to do it. if you are not generating errors, and the module is doing what you want, i would suggest you be the person waiting.

I like that suggestion, carlwhat, but we never really know for sure what a patch is addressing - perhaps it affects us. Regardless, my comment came off as snarky, which was inappropriate. Would like to edit/ remove that post. The plug-in is appreciated and well-maintained.

Hey LAT9 - I need to close the loop with you on my Sept post about our UPSXLM not getting our negotiated rates from UPS. Yeah - small businesses just breathlessly roll on to the next challenge. Thanks very much for your help - we got UPS's attention. When I presented this response code (that you spotted) to the UPS technical no-support people, they stopped saying its the shopping carts fault:

<RatedShipmentWarning>User Id and Shipper Number combination is not qualified to receive negotiated rates.</RatedShipmentWarning>

They took a good hard look at our UPS Account and figured out, yeah, something was not right....and FIXED it on UPS's end.

Great plugin you developed. And thanks again for the help.:clap:

Greg

You're welcome, Greg; I'm happy to have helped. Nothing like a little captured response code to show the "tech-no-support" people the error of their ways.

Oldy, moldy zc154

It's OK if the answer is "Rick get off your ######## and upgrade before stirring in this pot because looking at this is not a productive use of my time" :-)

I'm just wanted to have some functionality before I start the process with obtaining automated UPS rates for Stamps.com accounts. Past experience with Stamps.com tech folks have proven ineffective and don't expect any different now.

On standard checkout_shipping page:

10001: The XML document is not well formed
If you prefer to use ups as your shipping method, please contact SELLER.com via

CurlTester
Connecting to Zen Cart Support Server (https) ...
**Error **7: Failed to connect to https://www.zen-cart.com port 443: Connection refused

mydebug file:

[27-Feb-2020 11:41:34 America/Los_Angeles] Request URI: /9nd6Q536/modules.php?set=shipping&module=upsxml&action=edit, IP address: 98.146.164.107
#1  file_get_contents() called at [/home/chainwea/public_html/includes/functions/plugin_support.php:38]
#2  plugin_version_check_for_updates() called at [/home/chainwea/public_html/includes/modules/shipping/upsxml.php:57]
#3  upsxml->__construct() called at [/home/chainwea/public_html/9nd6Q536/modules.php:190]
--> PHP Warning: file_get_contents(http://www.zen-cart.com/downloads.php?do=versioncheck&id=126): failed to open stream: Connection refused in /home/chainwea/public_html/includes/functions/plugin_support.php on line 38.

[27-Feb-2020 11:41:34 America/Los_Angeles] Request URI: /9nd6Q536/modules.php?set=shipping&module=upsxml&action=edit, IP address: 98.146.164.107
#1  in_array() called at [/home/chainwea/public_html/includes/functions/plugin_support.php:42]
#2  plugin_version_check_for_updates() called at [/home/chainwea/public_html/includes/modules/shipping/upsxml.php:57]
#3  upsxml->__construct() called at [/home/chainwea/public_html/9nd6Q536/modules.php:190]
--> PHP Warning: in_array() expects parameter 2 to be array, null given in /home/chainwea/public_html/includes/functions/plugin_support.php on line 42.

[27-Feb-2020 11:41:35 America/Los_Angeles] Request URI: /9nd6Q536/modules.php?set=shipping&module=upsxml&action=edit, IP address: 98.146.164.107
#1  file_get_contents() called at [/home/chainwea/public_html/includes/functions/plugin_support.php:38]
#2  plugin_version_check_for_updates() called at [/home/chainwea/public_html/includes/modules/shipping/usps.php:117]
#3  usps->__construct() called at [/home/chainwea/public_html/9nd6Q536/modules.php:190]
--> PHP Warning: file_get_contents(http://www.zen-cart.com/downloads.php?do=versioncheck&id=1292): failed to open stream: Connection refused in /home/chainwea/public_html/includes/functions/plugin_support.php on line 38.

[27-Feb-2020 11:41:35 America/Los_Angeles] Request URI: /9nd6Q536/modules.php?set=shipping&module=upsxml&action=edit, IP address: 98.146.164.107
#1  in_array() called at [/home/chainwea/public_html/includes/functions/plugin_support.php:42]
#2  plugin_version_check_for_updates() called at [/home/chainwea/public_html/includes/modules/shipping/usps.php:117]
#3  usps->__construct() called at [/home/chainwea/public_html/9nd6Q536/modules.php:190]
--> PHP Warning: in_array() expects parameter 2 to be array, null given in /home/chainwea/public_html/includes/functions/plugin_support.php on line 42.

Upgrade won't help (although obviously you will want to do it at some point). The issue you are hitting is that there is something in the message you are sending which makes the XML invalid. Look for things like ampersands or quotes embedded in product names or perhaps in the customer's address.

TNX Scott,

Not sure what happened in the meantime but at least now I am getting UPSXML debugs in addition to the generic myDEBUGadm

swguy:

Upgrade won't help (although obviously you will want to do it at some point). The issue you are hitting is that there is something in the message you are sending which makes the XML invalid. Look for things like ampersands or quotes embedded in product names or perhaps in the customer's address.

what happens if mike d'antonio decides to order? can he not buy anything on the web? or what happens if mike d'antonio wants his product shipped to B&B Italia?

if the malformed XML document is due to one of those issues (and i'm not saying that it is not), then i think we should fix the plugin (or at least help lat9 with it).

are you sure you are using the latest version of the plugin?

Probably helps if I post the UPSXML debug instead of the zencart admin debug, though I don't know why the admin debug would have indications of UPSXML issues and also reference USPS in the same error. Admin error looks like zen-cart.com plugin support check is no longer supported

And to go along with carlwhat comments, I happen to live adjacent to the only town in the usa that has an apostrophe in the name but have learned to use a space instead.

Date and Time: 2020-02-27 15:24:15
UPS URL: https://onlinetools.ups.com:443/ups.app/xml/Rate
UPS Request: <?xml version="1.0"?>
<AccessRequest xml:lang="en-US">
   <AccessLicenseNumber>removedforsecurity</AccessLicenseNumber>
   <UserId>Chaingedforsecurity</UserId>
   <Password>8XRs2*xzt$KW&xb@</Password>
</AccessRequest>
<?xml version="1.0"?>
<RatingServiceSelectionRequest xml:lang="en-US">
   <Request>
       <TransactionReference>
           <CustomerContext>Rating and Service</CustomerContext>
           <XpciVersion>1.0001</XpciVersion>
       </TransactionReference>
       <RequestAction>Rate</RequestAction>
       <RequestOption>shop</RequestOption>
   </Request>
   <PickupType>
       <Code>03</Code>
   </PickupType>
   <Shipment>
<RateInformation><NegotiatedRatesIndicator /></RateInformation>
       <Shipper>
           <Address>
               <City>Hayden</City>
               <StateProvinceCode>LA</StateProvinceCode>
               <CountryCode>US</CountryCode>
               <PostalCode>83835</PostalCode>
           </Address>
<ShipperNumber>6digits</ShipperNumber>
       </Shipper>
       <ShipTo>
           <Address>
               <City>Hayden</City>
               <StateProvinceCode>ID</StateProvinceCode>
               <CountryCode>US</CountryCode>
               <PostalCode>83835</PostalCode>
<ResidentialAddressIndicator/>
           </Address>
       </ShipTo>
       <Package>
           <PackagingType>
               <Code>02</Code>
           </PackagingType>
           <PackageWeight>
               <UnitOfMeasurement>
                   <Code>LBS</Code>
               </UnitOfMeasurement>
               <Weight>1</Weight>
           </PackageWeight>
           <PackageServiceOptions>
               <InsuredValue>
                   <CurrencyCode>USD</CurrencyCode>
                   <MonetaryValue>142</MonetaryValue>
               </InsuredValue>
           </PackageServiceOptions>
       </Package>
   </Shipment>
   <CustomerClassification>
       <Code>04</Code>
   </CustomerClassification>
</RatingServiceSelectionRequest>

UPS RESPONSE: <?xml version="1.0"?>
<RatingServiceSelectionResponse><Response><TransactionReference><CustomerContext>Rating and Service</CustomerContext><XpciVersion>1.0001</XpciVersion></TransactionReference><ResponseStatusCode>0</ResponseStatusCode><ResponseStatusDescription>Failure</ResponseStatusDescription><Error><ErrorSeverity>Hard</ErrorSeverity><ErrorCode>10001</ErrorCode><ErrorDescription>The XML document is not well formed</ErrorDescription></Error></Response></RatingServiceSelectionResponse>

Sorry, should have said UPSXML v1.7.7

Production or Test server: same debug file

problem with your password....

try changing your password and removing the &xb

ahem.... ahem.... cough... cough....

best.

I can see UPS is gonna get me in trouble since there doesn't seem to be any way to differentiate Domestic GROUND from International GROUND as FEDEX allows that differentiation.

This is a troublemaker when it comes to allowing Canadian Customers to choose GROUND . 99% of Canadian Retail Customers do not understand that Customs Clearing is not included in the price and refuse the shipment when it arrives due to UPS Custom Clearing.

carlwhat:

problem with your password....

try changing your password and removing the &xb

ahem.... ahem.... cough... cough....

best.

UPS accepts that password when I login manually. I hate it when I have to manually 'dumb' my password generator.
BUT it is worth a try
TNX

nothing to do with UPS. it's the xml that does not meet validation prior to sending it to UPS. UPS is only telling you that.

as far as password security, removing the ampersand is hardly dumbing down the password... i think (and most experts would now agree) password length is the singlest biggest thing to having a stronger password. old school of utilizing 3 of the 4 character types is not nearly as secure as having a 25 character password.

carlwhat:

nothing to do with UPS. it's the xml that does not meet validation prior to sending it to UPS. UPS is only telling you that.

as far as password security, removing the ampersand is hardly dumbing down the password... i think (and most experts would now agree) password length is the singlest biggest thing to having a stronger password. old school of utilizing 3 of the 4 character types is not nearly as secure as having a 25 character password.

Progress. Thanks. That error has gone away when I changed the UPS password and replaced by another.

Shipping address from checkout screen

IMA Customer
9030 N Hess St 171
Hayden, ID 83835
United States

Or tried

MA Customer
123 main street
spokane, WA 99202
United States

UPS XML error thinks the address zipcode is in Louisiana???

111285: The postal code 83835 is invalid for LA United States.

RixStix:

Progress. Thanks. That error has gone away when I changed the UPS password and replaced by another.

Shipping address from checkout screen

Or tried

UPS XML error thinks the address zipcode is in Louisiana???

rick,
without the logs and specifically the xml that you are sending to UPS and the return string, it is hard to troubleshoot the problem.

UPS utilizes the USPS database of all US addresses. so if they are returning an error on address validation, then it is possible the USPS database has an error in its database.

with regards to the shipping addresses you have tried, the first address is a valid address, and it should come back fine. now because it did not, there is probably a problem with what you are sending them, which is why the logs are useful. that address validates as such:

Del address.. 9030 N HESS ST 171
Last line.... HAYDEN ID 83835-9827

Delivery point / check digit..... 30 4 Carrier route id.................. R008
eLOT sequence no / A/D code.... County.... KOOTENAI ID
FIPS state / county no......... 16 055 Congressional district........... ID 01
Early Warning System flag........... LACS indicator.......................
DPV confirmation indicator.......... S DPV CMRA indicator................... Y
DPV footnotes................ AA CC R1 DPV false positive indicator.........
Residential delivery indicator...... N LACS-Link ind / return code.......
Occupancy code...................... Suite-Link ind / return code......
Business/residential indicator...... Record type / default flag......... S
PMB designator / number.. Street match lev / sec adr flag.... S N

looks good to me.

the second address does not validate. there is no main st. there is a main ave, but the odd number addresses start at 127.

so, again UPS is utilizing the USPS database, and the odds that their coding is wrong is minimal. which is why we need to see the logs to interpret the problems.

best.

I appreciate the help. I thought the 2nd address might be invalid since I was going from a guess. The 1st, I know is correct because it is mine.

Regarding what is being transmitted, I havent a clue other than the data the upsxml mod pulls from the DB. I think that is the first part of the ups debug.... it has LA in it. Hmmm. TNX. Something for me to look at in the morning.