Mark - perhaps bug fix for upcoming 2.6.1 or so - SSL? Once activated, everything should be served over SSL. A user should not have to edit .htacces file or anything else, no?
The mixed content is due to the fact that you perhaps serve hard coded urls on your site? (html box or whatever?). The best way to include urls is to not use http:// or https:// in front of the URL.
Use // only, so if you link to an image which is hosted on your site, then do it like this: <img src="//domain.com/image.jpg">
In this case the url will automatically http OR https depending on your configuration
So first you need to check what the mixed content is.. you can do that via the the in... moreThe mixed content is due to the fact that you perhaps serve hard coded urls on your site? (html box or whatever?). The best way to include urls is to not use http:// or https:// in front of the URL.
Use // only, so if you link to an image which is hosted on your site, then do it like this: <img src="//domain.com/image.jpg">
In this case the url will automatically http OR https depending on your configuration
So first you need to check what the mixed content is.. you can do that via the the inspect element of your browser and change the urls
Question @ketkew ... on the string <img src="//domain.com/image.jpg">, why wouldn't you just soft code it to /image.jpg and drop the //domain.com? Once on the sites domain anything after the .com is not needed to navigate. I have every link on my site soft coded to anything that comes after the .com and experience no https issues.
