Fast and Easy Checkout

[rwoody]

I'm having the same problems...

No warnings or explanations that a credit card transaction has failed -- it just jumps back to the payment page with the credit card details blank.

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

[numinix]

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.

[yardsale]

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.

Hello Numinix,

Which payment modules did you fix?

[rwoody]

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.

In patching payment modules, it would have seem logical to patch those that are released as core to Zen-Cart first, as the Authorizenet module is just that, part of the core.

Also, I know that you do this as an accommodation and the contribution is freely distributed, and for that I'm very appreciative; however it might be a good idea in your notes for either installation or d/l to state as such this as a known bug and indicate processors that you are aware of that are not fully compatible. We have determined that this has cost my customer thousands of dollars in sales.

I'm not sure why, but I found that merely turning off the contribution does not fully return the system back to the original checkout as I am still not able to see the proper error message for this particular error (I did receive an error for a bad cc # in my testing). Apparently it will be necessary to completely remove the contribution from the system.

I'm going to see if I can find anyway to solve this as my customer truly loves your contribution and does not want the long version put back into place. If I'm fortunate enough to figure this out, I will post the solution here.

Thanks again for your effort, and please do not think that I'm being overly critical. I know how hard it was to get this to work as well as it does, as I personally, before your contribution was released under-took building such a modification and due to issues such as this gave up. (too many bugs). So I do appreciate your hard work and applaud you for it.

Thanks again!

Ruth

[Liza_with_a_Z]

Hello!

I have done a fresh install of both ZC and FEC (latest rev) - getting errors on checkout page:

COWOA_HEADING
TEXT_RATHER_COWOA

TABLE_HEADING_BILLING_ADDRESS
ENTRY_COPYBILLING

TABLE_HEADING_SHIPPING_ADDRESS

Any helpers?

[Liza_with_a_Z]

Hello!

I have done a fresh install of both ZC and FEC (latest rev) - getting errors on checkout page:

COWOA_HEADING
TEXT_RATHER_COWOA

TABLE_HEADING_BILLING_ADDRESS
ENTRY_COPYBILLING

TABLE_HEADING_SHIPPING_ADDRESS

Any helpers?

FIXED!

My bad - did not see that I needed to change YOUR TEMPLATE under Includes too. Uploaded and text issues resolved.

[numinix]

In patching payment modules, it would have seem logical to patch those that are released as core to Zen-Cart first, as the Authorizenet module is just that, part of the core.

Also, I know that you do this as an accommodation and the contribution is freely distributed, and for that I'm very appreciative; however it might be a good idea in your notes for either installation or d/l to state as such this as a known bug and indicate processors that you are aware of that are not fully compatible. We have determined that this has cost my customer thousands of dollars in sales.

I'm not sure why, but I found that merely turning off the contribution does not fully return the system back to the original checkout as I am still not able to see the proper error message for this particular error (I did receive an error for a bad cc # in my testing). Apparently it will be necessary to completely remove the contribution from the system.

I'm going to see if I can find anyway to solve this as my customer truly loves your contribution and does not want the long version put back into place. If I'm fortunate enough to figure this out, I will post the solution here.

Thanks again for your effort, and please do not think that I'm being overly critical. I know how hard it was to get this to work as well as it does, as I personally, before your contribution was released under-took building such a modification and due to issues such as this gave up. (too many bugs). So I do appreciate your hard work and applaud you for it.

Thanks again!

Ruth

As of the latest version, there are no payment module issues.

[shartlesville]

I upgraded to 1.4.6 and now the gift certificates won't work at all. It just refreshes the page adding or subtracting the GC amount each time but it won't go to confirmation. I temporarily disabled it.

Before the upgrade they worked normally but I had an issue with $0 totals using coupons - it turns out it is a built in Zen Cart thing. Now the GC do not work.

Thank you for any assistance you can provide.

Blessings,
Krisann

[Liza_with_a_Z]

I have an IE6 bug that I don't seem to see a fix for.

When you buy anything and click on the process order button I get an "The page cannot be displayed" error. It is trying to load index.php?main_page=fec_confirmation

I have set up a clean install with zencart 1.3.8a and FEC 1.4.2 to show the problem. You can go to
https://www.yabyummy.com/test/learn/
and add anything to your cart. It works on all browsers I have tested except IE6. I would really like a fix since a lot of people still use IE6 and it is very scary to a customer to click the process order button and receive an error.

Please Help

I have a clean install also - Is there a solution to this?

[Liza_with_a_Z]

I have a clean install also - Is there a solution to this?

The exact error in IE is:
Internet Explorer cannot open the Internet site
http://xxx/index.php?main_page=fec_confirmation.