Checkout pages secured?

[JDog21]

I am configuring my SSL. I have secured my admin, and set the "true" setting for my checkout pages being secured, as well.

Although my admin is now secure (with https in address), simulated transactions do not result in ssl pages at any point throughout the checkout process.

I suspect this is some simple thing, but other than change my config.php file in my includes, and do not know of any other thing to do in order to secure my checkout pages....

I appreciate any help......

vers. 1.3.9a

[terraGirl]

Without a URL to test it's tricky to say.

Normally, changing /includes/configure.php is all you need to do. The key entries are:

define('HTTPS_SERVER', 'https://www.yourdomain.com'); // note the HTTPS address
define('ENABLE_SSL', 'true');

A less common issue is a template which over-rides links with http links. As long as the standard Zen Cart link function is used, you should be fine.

[DrByte]

When you make changes to your configure.php files, remember that those files are normally read-only on the server, meaning no changes will be saved unless you first make the files writable. Then upload the changes and make those files read-only again.

[JDog21]

I've checked file permissions, and I've modified admin/includes/configure.php and store/includes/configure.php for SSL

When I go to the login page for admin, there is an https in the address. Same for rest of admin pages.

When I check out, though, there is no https. in the address. All the way through, including the page where you enter a credit card number.

Can a page be protected and still not have an https in it's address? How do you check? I want the https. to be there. I want customers to see it.

Can being in test mode with authorize.net have something to do with this?

Could GoDaddy have set up the SSL incorrectly?

[DrByte]

When I check out, though, there is no https. in the address. All the way through, including the page where you enter a credit card number.

What about the store login page?

Can a page be protected and still not have an https in it's address?

No.

Can being in test mode with authorize.net have something to do with this?

Not at all.

Could GoDaddy have set up the SSL incorrectly?

Maybe. Wouldn't be the first time.
But that may have nothing to do with the problem you're reporting.


How EXACTLY are you going about editing the /includes/configure.php file on your server?

[JDog21]

I figured it out.....

I simply had to stare at it long enough, and eventually it became visible......

the define the https parameter had http://myssite.com

I just had to add an s. https://mysite.com


My mistake......I'm learning..........