Quote Originally Posted by rwoody View Post
Ok, I guess this makes Three of us. I had never noticed this before until my customer advised me of his customers having checkout issues with the checkout looping.

Typically it is caused due to the shopper not entering the correct billing address and upon making that correction - the processing goes through.

I need an error message to indicate to them that is the issue so they can, on their own, make the correction without wondering what has happened or calling customer service.

I did a test with debug on and there is in fact an error message indicated, but not being displayed. I'm wondering if the bit of code from the original checkout for posting the error message was overlooked.

I'm going to check and see what I can find - if anyone can direct me to where I might look for that it would be a huge help.

Thanks

Ruth
yes, we know of the bug and have fixed it for most payment modules. But in a discussion with DrByte, the payment_error parameter is going to be deprecated in 2.0 and only messageStack will be used. Because of all the redirects FEC uses, the messageStack error is lost and so no error is displayed. Once we have a solution for modules like PayPal WPP, we will release the new version. The alternative is to have any returns to the checkout due to payment issues, to simply default back to the regular checkout_payment module. But we'd rather find a solution to keep customers in FEC and have the one click option.