My SSL certificate is installed correctly, but some of the content is giving Chrome trouble because its being delivered via http instead of https. Chrome developer tools seems to implicate the font function as the string it doesn’t like:
font-family: ‘Terminal Dosis’;
src: local(‘Dosis Regular’), local(‘Dosis-Regular’), url(‘http://themes.googleusercontent.com/static/fonts/terminaldosis/v5/_IcvjW_kWHsIHjjUsLbdpKti5uXGbodo2Scs19s1bWs.woff’) format(‘woff’);
any tips on where I can track this down in the template so I can force it to SSL?
You can change the http to https in the framework>js>avia_advanced_form_elements.js file. Search for:
You’ll see the href link that gets added and can modify it.
Also open up the class-style-generator.php in the php folder (inside framework) and search for:
Do the same thing for the link inside that function (change http to https).
Save everything and put the files back onto the server. I’ve not gone through the steps myself as I don’t have a ssl cert set up on my live server so be sure to let us know if it doesn’t do the trick (and if it does).
The topic ‘Google fonts causing SSL issue’ is closed to new replies.