Hi all, I'm using Ubercart 2.2 with the Skipjack payment module, and connecting to the development processor.
When I attempt to process an order, it says that it's unable to process the credit card, but when you look at the logs the error is simply that a shipping phone number wasn't specified. When I go into the order and enter a number into this field, I am able to run the transaction.
Initially, I had this problem without even having the shipping module enabled, but I've since enabled that to see if that would fix it. I also tried requiring a billing phone number, but that didn't help, since of course it's looking for the shipping phone number, which doesn't exist because I don't want people to have to enter shipping information for a video download.
At this point, I've set up my products as non-shippable, and the billing phone number isn't required.
I also have the checkout process set up to hide shipping information for users whose carts only include non-shippable products.
Any ideas about how to fix this weird problem?
Comments
Comment #1
longwaveAccording to page 27 of the Skipjack Integration Guide, the "shiptophone" field is required for all transactions. I am not sure what Skipjack expect to you to do here if you do not have any shippable products in your order - perhaps you should contact them and ask if it is acceptable to send the billing phone number instead in this field?
Comment #2
finhirschoff commentedI've fixed this for the meantime by changing the module so it sends a dummy phone number, which is what they suggest in their documentation. It would take a bit more work to get it to only send a dummy number when there wasn't a shipping number specified, but that would be the real fix for this.
Comment #3
longwaveLeaving this "active" for now so other users can find this problem more easily and so there's a place to post a patch if anyone wishes to do so.
Comment #4
micheleannj commentedFor some reason this bug just started effecting our site. I edited the module to use billing phone as shipping phone. Could you clarify if your work-around is supposed to be in the 6-1.x version or should I submit a patch?
Thanks!
M
Comment #5
longwaveThere is no code to handle this in 6.x at present. A patch should be trivial but I am not currently using this module in production, so would prefer a tested patch to come from someone who actually does use the module.
Comment #6
longwaveFixed in 6.x-1.1.