FEDEX Response parsing errors

I have had a couple sites using the fedex calculator having shipping fail recently.
In looking at the response from fedex, it looked like a rate was sent, but eCart was not properly parsing the response.
I am using 5.06, so the most current release.
After a couple hours of tweaking and trying a few things, it looks like the xml structure has changed slightly?
To get a successful response, I had to change line 334 from
$respCode = (isset($WA_FedEx_params["V10:SEVERITY"]) && ($WA_FedEx_params["V10:SEVERITY"] == "SUCCESS")?1:0);

to
$respCode = (isset($WA_FedEx_params["V10:NOTIFICATIONS"]["V10:SEVERITY"]) && ($WA_FedEx_params["V10:NOTIFICATIONS"]["V10:SEVERITY"] == "SUCCESS")?1:0);

(severity was nested inside the notifications node)

and to get the rate, I had to change line 353 from
$_SESSION[$FedEx_eCart->CartName . "_FedEx" . "_Quote"] += ($WA_FedEx_params["V10:RATEDSHIPMENTDETAILS"]["V10:SHIPMENTRATEDETAIL"]["V10:TOTALNETCHARGE"]["V10:AMOUNT"]);

to
$_SESSION[$FedEx_eCart->CartName . "_FedEx" . "_Quote"] += ($WA_FedEx_params["V10:RATEREPLYDETAILS"]["V10:RATEDSHIPMENTDETAILS"]["V10:SHIPMENTRATEDETAIL"]["V10:TOTALNETCHARGE"]["V10:AMOUNT"]);

The amount was nested inside the RATEREPLYDETAILS node.

Is anyone else experiencing this?

Tom

here is an updated copy of the WA_eCart/WA_eCart_FedEx_PHP.php file that should correct the issue, an update is being released later today or early tomorrow that will include this fix.

Was this a known, new issue? Or has it been going on for a while?

we discovered it only recently.

Jason.
Heh... perhaps I should have asked sooner, instead of spending a couple hours figuring a work around myself. :-)

I did look in the forum, and the download page, and didnt see a mention of an issue, so I plowed ahead and made my own fix.

Its functional, but yours is a little more elegant.

Is this due to a change in the way Fedex formats their response recently?
Just curious, since its easier to pass on the time to clients if I can tell them it was due to a Fedex Change.

Thanks,
Tom

yes, it was caused by a change that fed ex implemented in their API.