Jump to content

{$base_dir} question


Recommended Posts

Hello, on my order.php page IE throws up non SSL Certificate errors.

If I look at the source code, there are a number of links to the SiteMap, Contact form etc etc which are all showing as http:// rather than https://

Firstly, links like this will not pull errors will they? I thought it was things trying to load into the page from a non-ssl source that would throw the error.

In the header file these all use {$base_dir} .. .Is this the correct parameter. I see there are {$base_dir_ssl} parameters under the account login links.

Some of my Search Form links and subscribe to newsletter are posting to http pages, but besides this there is nothing loading in from a non-ssl source... unless its google analytics tracking code pulling the error?

Thanks for any help

Link to comment
Share on other sites

  • 3 weeks later...

Run the whole shop in https mode?

think you could just set the URL in your config settings file.

I know prestashop is made to kick in and out of http and https mode if https mode is set in the admin.. .so im not sure if you would find this "non-secure content" error on some of your pages if you run it all in https mode.

Have a go.

Link to comment
Share on other sites

bartman, thanks for the note. Yes the SSL problem with some content not being in secure mode was only in IE.
FF, Chrome, Safari etc were all fine with it.

Were you viewing the site in IE?

Thanks for the note on newsletter stuff, Ill go change now.

Link to comment
Share on other sites

  • 1 year later...

Go to your header.tpl file and change the {$base_dir} to {$base_dir_ssl} where ever needed. To find the location of the errors use Googe Chrome and go to the page with the error. Then click on the 'wrench menu' in the upper right corner of Chrome and click on tools > JavaScript Console. This will show you where the errors are.

 

The fix for me was in my header.tpl because that was the file pulling files from http and not all https.

 

Link to comment
Share on other sites

  • 2 years later...

Go to your header.tpl file and change the {$base_dir} to {$base_dir_ssl} where ever needed. To find the location of the errors use Googe Chrome and go to the page with the error. Then click on the 'wrench menu' in the upper right corner of Chrome and click on tools > JavaScript Console. This will show you where the errors are.

 

The fix for me was in my header.tpl because that was the file pulling files from http and not all https.

 

That is a fix indeed. Not a solution.

When will there be a proper solution by Prestashop? My expensive ev ssl certificate looks very silly right now :(

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...