PDA

View Full Version : checkout page doesn't refresh right on first attempt when using SSL

jroxonline
09-08-2004, 08:49 PM
when you use SSL to checkout in the shopping cart, the first page, when it asks you whether you're a new/returning customer, all of the data doesn't come up. Mostly the text of the page is missing. when you refresh it or go back, that's when it all comes up. it works fine when you don't use SSL however.

I've tested it on a few different boxes, and it all comes up the same - no text initially. I used WinXP with IE6, Win2000SP4 with IE6 and WinXP with Firefox 0.9.2.

by the way, I am testing it with a shared SSL Certificate...

any ideas?
jroxonline
09-09-2004, 01:39 PM
any support on this?
Cameron Allen
09-09-2004, 01:49 PM
Could you private message me a soholaunch login? If this bug is indeed apart of 4.7, it will be fixed and released by tomorrow.
jroxonline
09-13-2004, 08:46 PM
looks like you guys fixed the issue with viewing invoices using a shared SSL certificate with the new soholaunch code, but it looks like you haven't addressed the issue yet with the shopping cart page text missing on first checkout.

I just tried it and it still does the same thing. the text is missing unless you refresh it manually.

any updates on this?
Ruben
09-13-2004, 09:05 PM
im having the same problem rjoxonline. im sure they are working on it.

Ruben
Cameron Allen
09-13-2004, 09:10 PM
This along with a few more bugs will be fixed in the next build.
jroxonline
10-19-2004, 08:10 PM
I've recently installed the latest build, but this bug is still there. is there a time table for this to be fixed?
Cameron Allen
10-20-2004, 01:38 PM
Mike said this will be fixed on the Nov. 3 release. We will patch this up as soon as possible.
Ruben
11-20-2004, 10:32 PM
Cameron, I just mailed you about the same problem. together with the problem that (when SSL enabled) im not able to view any invoices.
when turning off SSL everything works ok.
Cameron Allen
11-22-2004, 02:06 PM
I thought this was fixxed, but it appears otherwise. I will see what we can do about getting this fixxed intime for todays bug-fix release. If we can't get it fixxed intime for that we will get this in the the next release which should be eiter friday, or sometime nextweek.