You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
Hi gang,
I've got a minor issue I'd like to resolve. If you start a checkout on my site, fill in all your information, continue through the checkout, but then decide to go back to shopping; when you return to the checkout, your information is not filled in for you. Isn't the session cookie supposed to do that? I'm running the ATS SEO mod, and I've read about issues with cookies disabled. But I am able to add multiple items to the cart and the cart is kept, so I don't think that's the issue. Also, if I send a contact message and then go back to the contact page, the information is filled in there. Do I have a setting wrong somewhere? Does the checkout not populate the information because I'm using the secure checkout? Any thoughts?
Thanks,
Rachael
Offline
That's inherent in the design of SSL. Presumably since you're using SSL the data is sensitive and should not be cached for automatic re-display.
Ideally CCP would collect the address information (first page of checkout) outside of the secure server, then the address info could be pre-filled. It's silly as it is.
Offline
Thanks for the response. I think I understand what you're saying. But I thought ste_chkout.pl automatically prefilled the form fields. I.e.:
<INPUT type="text" value="tracking_firstname">
Shouldn't that work regardless of SSL or does the SSL actually stop the field from taking the initial value assigned to it?
Rachael
Offline
Nick's post, second from the bottom, in features a mod that allows for cookies in SSL, however I believe it only works if the non-secure and secure domains are the same (http/https versions with same domain names).
Offline
Thanks Ed, that explains it now completely. That might just provide the motivation for me to get off shared SSL and get my own cert.
Thanks!
Rachael
Offline
Two months later I see your post, Rachael. If you haven't gotten your own SSL yet, the Thawte 123 is only about $35/yr at . Beats the $100+/yr that we used to pay directly to Thawte.
Offline
Thanks for the reply! I did end up getting my own SSL certificate... as part of a server move about a month ago. Thanks for the information, though - I'll keep that in mind at renewal time!
Rachael
Offline
If I under stand this right what your ar saying is that every time you continue shopping when you want to check out you have to log back in to get to the shopping check out screen.
If this is what is happening, I also have the ATS SEO mod and had this problem. I contacted ATS and they put in some code that fixed this problem for the most part, I still see problems with Apples Safari not keeping the loged in info.
The way that ATS salved this is that there are two cookies involved one session cookie and one fd_act cookie which keeps the customer loged in untile they click on a log out link. The trouble with Safari is that it only gets one cookie which is the session one which keeps the customers cart information.
John
Offline
I just want to confirm the code changes from Nick before I make the mod. Does he mean replace with as below?
In that file you're looking for:
(1) In the routine 'ste_usr':
if ($fd_secure ne "Y" && $fd_pg !~ /^ste_nolay_redir/) {
Change to:
if ($fd_pg !~ /^ste_nolay_redir/) {
(2) In the routine 'ste_usr_check':
if ($fd_secure ne "Y") { $set_usr_cookie = "Y"; } ######### End of if statement.
Change to:
$set_usr_cookie = "Y";
(3) In the routine 'ste_usr_check_act':
if ($fd_secure ne "Y") { $set_usr_cookie = "Y"; } ######### End of if statement.
Change to:
$set_usr_cookie = "Y";
(4) In the routine 'ste_usr_check_aff':
if ($fd_secure ne "Y") { $set_usr_cookie = "Y"; } ######### End of if statement.
Change to:
$set_usr_cookie = "Y";
I also have the ATS batch and do not believe that it was the cause of the lost data. I had noticed the problem because I had put a personalized message at the top of my checkout and regular store pages. I lost the customer name when they went over to secure side.
I was also having the problem that my wholesale mod was losing dealers on the secure side and therefore they could not see the wholesale pricing unless they logged in. I put a bandaid on this by placing a login window on my store and cart pages. Once they logged in, they could go back and forth because they were technically logged in in two places...unsecured and secured side. I think for those that are on two different servers, this is the way to go.
The above is the best solution in my mind.
Regards,
Bob
Offline
My problem was not related to user accounts - I don't use them. I originally posted wanting to understand why the checkout wouldn't get user's information from their cookie if it had previously been entered (like if they started the checkout, went back to shopping, and came back to the checkout). The explanation about the secure side not using the cookie cleared things up for me. I implemented the mod from Nick, just as is posted here, and it worked great for me. My checkout page now keeps the user's data if they leave and come back to it. But I can't offer any insight into how well this will (or won't) work for user accounts or wholesale accounts. And to answer your question, Bob, you are reading it correctly. Where nick says "Change to", he means replace the first code with the second, just as you've indicated in red.
Rachael
Offline
I went ahead and implimented the changes and it works fine for customers and wholesale. I actually noticed some transactional speedup on my one-page checkout as well.
Bob
Offline