Bug: Merchant handling of Require Shipping [x]

[RayYates]

If this has not been fixed please add it to the list.

If a store has the Require Shipping [x] box checked and is using a module like Viking FedX Advanced or any other module that queries a remote server to get methods...

You can get the following Fatal Error

Error Code: MER-SUI-MMU-00002 Description: Shipping Selection is required and no shipping methods were found. Please contact the administrator directly.

To trigger this error, select a state then enter zipcode from another state durring checkout.

The Shipper can not return any valid shipping methods so the module returns none to Merchant.

Rather than displaying a "red" onscreen error message, Merchant throws up the fatal error above. The customer has no idea what to do an will likely abandon the basket.

[wcw]

Re: Bug: Merchant handling of Require Shipping [x]

I ran into this the other day. The store had my sort shipping plus free shipping options module which has a default shipping method if there are no others available. But it was not even allowed to run. It runs in the component initialize function but that function did not even get called for the OSEL page because the fatal error was activated before the OSEL page started. That whole check for no shipping method should be run in the Action = SHIP which occurs when the continue button is clicked on the OSEL page. Course if a hacker is re-writing a form and omitting the SHIP action, then that would not work. There has to be a way to let the OSEL page display before bombing out.

[Rick Wilson]

Re: Bug: Merchant handling of Require Shipping [x]

That's a good catch, I'll pass this on.