Quote:
|
Originally Posted by albertchui
i am not familiar with that, do you know what file need to be adjusted, i contacted them and seems they denied it's their image path caused it, below is their respond:
We use the same signin/register links as the standard X-Cart skins use.
Just compare 2 files:
/skin/common_files/customer/authbox.tpl
/skin/xtreme_gear/customer/authbox.tpl
and you will see that there is no difference.
|
No. The insecure images on https pages have nothing to do with those files.
The images that xtreme still serves http when secure are in the file,
/skin/xtreme_gear/customer/banners-quicklinks.tpl
Some of these images, are served as http, even on https pages.
Simply re-code the offending images using relative image paths, such as:
<img src="{$AltImagesDir}/custom/image-name.png" width="280" height="150" alt="image name" title="image title" />
Obviously, this an oversimplification.
What you need to do:
1. Go to the https page that is tossing the error.
2. View page source.
3. Search for "http:" -- you will see the offending image(s)
4. Change the paths to the offending images so they use a relative path, such as {$AltImagesDir}
You may also find insecure images served from file:
/skin/xtreme_gear/customer/head.tpl
(the header logo)
The <problem> here is that xtreme interface is very convenient -- and easy to add/change images -- so use the tool for development -- then hard code the relative image paths once you like your design.
These images should not be served from an absolute path if they will be used on an https page. Easy enough to fix.