VirtueMart Forum

VirtueMart 1.1.x [ Old version - no longer supported ] => Security (https) / Performance / SEO/ SEF issues VM 1.1 => Topic started by: v2interactive on August 02, 2010, 15:43:48 pm

Title: shared SSL + hostgator store = https:// problems
Post by: v2interactive on August 02, 2010, 15:43:48 pm
Hi,

I have another problem.  I'm using hostgator on a site with VM.  I purchased their SSL and it works fine... kind of...  I noticed when I go to my site in https mode:

https://www.valtorc.com I get an error in IE that says:

"This webpage contains content that will not be delivered using secure https connetion, which could compromise the security of the entire webpage"

Now, I know this error is because of my config file saying http://www. instead of https://www. I know that much.

But here's my problem, I JUST want the ecommerce section to load https, which I also know can be done through the VM config. but then again, my joomla config I would assume specifies http://

Has anybody had this problem before?  I've searched for days with nothing.

Please help :(
Title: Re: shared SSL + hostgator store = https:// problems
Post by: filterit on August 02, 2010, 20:39:34 pm
I had this problem.

It was down to a module that I had added.  Most of the shopping page was https but this module was just loading as http.
Look at the source code generated for that page and see the http:// offending url, this should give you an indication of the problem module.
Title: Re: shared SSL + hostgator store = https:// problems
Post by: uandme90 on August 06, 2014, 15:24:12 pm
Same problem for me too .In 2008 I have developed ecommerce site and to secure it i bought ssl-certificates from symmentics .Igot problem of swiching between http and https which i don't like . so Now i bought another ssl certificate from globalsign which is fine .
Title: Re: shared SSL + hostgator store = https:// problems
Post by: Peter Pillen on August 07, 2014, 14:28:50 pm
You need to look in the source code after files, images or links that are coming by non-ssl urls. Search the code for any http:// and look up where it is coming from (module, plugin, template, ...). That way you can change it to https version. Only if all links on a page are https://, the error message will disappear.