Issues with onepagecheckout.asp

Hello,

We are building a website at a development location and we just got the SSL Cert. installed, and the Merchant Account plugged in.

I attempted to run a few test orders several days ago, and I noticed on the 'onepagecheckout.asp' page, that after I put in my address, etc, and click 'Continue', nothing happens.  The page just seems to refresh, and the spryaccordian does not fold out to show credit card info.

I was running v4.0 sp3, so I upgraded to SP4.  I did this, and it did not fix the problem. 

I then temporarily restored the header/footer files, and it looks like that fixed it, however I can't quite figure out what the difference is.

Also if I attempt to check out as 'guest' - after I fill out my address info and click 'continue', it redirects me back to the checkout page again.

On top of that - if I attempt to login to my account and click continue, not only does it just refresh the page - but my user name & password info become available in the address bar.

You guys can check it out here if you'd like:

http://gem-tech.com.mytempweb.com/store/pc/onepagecheckout.asp

Any help would be GREATLY appreciated,
Thanks

Matt wrote: Your header has conflicting code.  It is probably JavaScript.  Otherwise, it could be a custom sign-up form that uses the same field name as something in OPC.  I hope that helps.

Thank you very much Matt, I appreciate your time and help.  I will examine all the JS and try to pinpoint it.


Thanks,

We're running 4.1a SP2 on our DEV site as of today, and are having the same issue, more or less.

Clicking Continue after confirming the Billing Address results in an popup alert that says "There was an unexpected problem updating your order. Please contact us so we can help save your order, or try again."

Then the page auto-refreshes and populates the URL with the customer information.

I've tried removing every bit of extraneous Javascript but that doesn't seem to be the issue.

I've tried it with current versions of Safari, Firefox and Chrome on MacOS 10.5.8 with the same results.

Any thoughts or should I be raising a ticket?



Edited by rotokirby - 09-June-2011 at 8:15pm