bluewt
Forum Replies Created
-
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] Http to Https: unsecure due to font issue?In my case, this issue was caused by my caching plugin (W3 Total Cache). Disabling it solved the issue but you may want to keep the plugin and change the font URLs in the CSS file from HTTP to HTTPS.
I came across this issue when the Social Pug plugin stopped showing icons on the social media buttons. The root cause was the caching enabled by W3 Total Cache plugin. If you are in a similar situation, there are three ways to fix the issue:
– Disable W3 Total Cache (not recommended because your website’s performance may decrease)
– Change the font URLs of Social Pug plugin to HTTPS
– In some cases, URL Rewrite rules may cause this issue. Check your .htaccess fileMixed Content: The page was loaded over HTTPS, but requested an insecure font
- This reply was modified 7 years, 3 months ago by bluewt.
@gixxer188, did you try removing those lines from functions.php which is in your template folder (wp-content\themes\templatename\)?
Thanks guys. I finally found it in templatename/functions.php
It was resolved. I don’t know how. I’ve just done some remove/upload and deactivate/activate stuff. I think the problem was related to MySQL database or hosting.