Title: Fix https insecure warnings
Last modified: January 3, 2017

---

# Fix https insecure warnings

 *  [SpeakOut! Steve](https://wordpress.org/support/users/123host/)
 * (@123host)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/fix-https-insecure-warnings/)
 * If you are moving to https:// (and you should be) you may find you get loads 
   of insecure content warnings `'(page) was loaded over HTTPS, but requested an
   insecure stylesheet 'http://fonts.googleapis.com/css?family=Quicksand|Open+Sans'.
   This request has been blocked; the content must be served over HTTPS`
 * This is caused by some hard coding that would likely have been fixed if this 
   plugin was being maintained. It was painful to find 😛
 * Here is how you can fix this yourself.
 * You need to edit 3 files –
    /wp-content/plugins/recipe-card/js/post.js /wp-content/
   plugins/recipe-card/js/theme.js /wp-content/plugins/recipe-card/yumprint-recipe.
   php
 * In each of them search for _[http://fonts.google](http://fonts.google)_ and insert
   an _s_ to make it _http**s**://fonts.google_
 * The files are minimised so they are pretty difficult to read as they aren’t formatted
   well, but doing a search will find it.
 * This worked to solve the issue on a site with many recipes.

The topic ‘Fix https insecure warnings’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/recipe-card_cfc7c6.svg)
 * [Recipe Card](https://wordpress.org/plugins/recipe-card/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/recipe-card/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/recipe-card/)
 * [Active Topics](https://wordpress.org/support/plugin/recipe-card/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/recipe-card/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/recipe-card/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [SpeakOut! Steve](https://wordpress.org/support/users/123host/)
 * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/fix-https-insecure-warnings/)
 * Status: not resolved