Title: Broken HTTPS with Pro version of the plugin
Last modified: August 30, 2016

---

# Broken HTTPS with Pro version of the plugin

 *  Resolved [meijin2k](https://wordpress.org/support/users/meijin2k/)
 * (@meijin2k)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/broken-https-with-pro-version-of-the-plugin/)
 * Hello! I sent in a request via email 2 days ago, but have not heard anything 
   back yet. I thought that maybe I should post it here? This is in regards to the
   Pro version of the plugin.
 * Just so you know, I am running v4.2.5 of WordPress along with Woocommerce and
   W3 Total Cache (W3TC) along with caching everything on CloudFlare. We have our
   own site certificate. You should also be aware that I am pretty much a newbie
   who knows just enough to be dangerous.
 * As soon as I implement the Uji Countdown Premium plugin, it breaks the HTTPS 
   on my site. When I use the “Inspect Element” function in Chrome, I see the following:
 * Mixed Content: The page at ‘[https://www.mysite.com/&#8217](https://www.mysite.com/&#8217);
   was loaded over HTTPS, but requested an insecure stylesheet ‘[http://fonts.googleapis.com/css?family=Aldrich&#8217](http://fonts.googleapis.com/css?family=Aldrich&#8217);.
   This request has been blocked; the content must be served over HTTPS.
 * Please note that I obscured my domain as I don’t want anyone to think I am trying
   to drive traffic or create a backlink or anything. I am happy to give you the
   direct link.
 * Also please note that when I leave the font in Uji set to default, I get the 
   same error. Only it says “family=None” or “family=Default”. I forget which. I
   think it is “default”.
 * So, I have a DEV or sandbox site that is an exact duplicate of the main or live
   site. In researching this issue on the interwebs, I found a link that indicated
   using “protocol relative links” and to add the following to the functions.php:
 * function mytheme_enqueue_styles() {
    wp_register_style(‘googleFonts’, ‘//fonts.
   googleapis.com/css?family=Copse’); wp_enqueue_style( ‘googleFonts’); }
 * So I added this to the functions.php file of my child theme (Flatsome theme BTW,
   don’t think I mentioned that). I purged the cache in W3TC and reloaded the page
   and the errors when away when checked in “Inspect Element”. Short lived happiness
   though….keep in mind that the DEV site does not use CloudFlare, just the live
   site.
 * When I did the same on my live site, the error persists. Nothing I do will get
   rid of it. I am not sure if CloudFlare caches the functions.php file, but I still
   tried to purge that file. I purged the home page. Nothing.
 * So, I know while this appears to be a caching issue with CloudFlare (and I have
   just submitted a ticket to them…but they can be a little slow to respond), I 
   am hoping and praying that there is a way to fix this with you. After all, caching
   with sites such as CloudFlare is getting more and more popular and alot of sites
   use them. I am hoping there is a fix I can do or there is some way that you might
   be able to modify your plugin such that HTTPS is not broken when the plugin is
   used in conjunction with 3rd party caching.
 * Can you help?
 * Thank you for your time and assistance.
 * [https://wordpress.org/plugins/uji-countdown/](https://wordpress.org/plugins/uji-countdown/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Thread Starter [meijin2k](https://wordpress.org/support/users/meijin2k/)
 * (@meijin2k)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/broken-https-with-pro-version-of-the-plugin/#post-6553228)
 * One week with a post here and 2 emails into the author and not a peep…and this
   is the for the paid version…not good. Not good at all.
 *  Plugin Author [Activity Track](https://wordpress.org/support/users/ujimoto/)
 * (@ujimoto)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/broken-https-with-pro-version-of-the-plugin/#post-6553230)
 * Hi meijin2k,
    I’m truly sorry but never got your emails. I will do an updated
   this week to fix the https protocol instead of http. Also I wanted to let you
   know I have similar isuue with CloudFlare but not for this plugin or other plugins.
 *  Thread Starter [meijin2k](https://wordpress.org/support/users/meijin2k/)
 * (@meijin2k)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/broken-https-with-pro-version-of-the-plugin/#post-6553245)
 * Whatever the communication break down was, I am happy that ujimoto was able to
   reach out to me and today provided me with a solution that corrected the HTTPS
   issue I was having. It is appreciate more than you know.
 * Installed the new plugin update and it appears that HTTPS is back to fully functional
   on my site.
 * Well done sir and thank you!
 *  Plugin Author [Activity Track](https://wordpress.org/support/users/ujimoto/)
 * (@ujimoto)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/broken-https-with-pro-version-of-the-plugin/#post-6553246)
 * Thank you meijin2k for reporting this bug and the detailed information you provided.
   All the versions are now updated. Please download the latest version 2.0.5 in
   order to fix this issue.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Broken HTTPS with Pro version of the plugin’ is closed to new replies.

 * ![](https://ps.w.org/uji-countdown/assets/icon-256x256.jpg?rev=1074703)
 * [Uji Countdown](https://wordpress.org/plugins/uji-countdown/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/uji-countdown/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/uji-countdown/)
 * [Active Topics](https://wordpress.org/support/plugin/uji-countdown/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/uji-countdown/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/uji-countdown/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Activity Track](https://wordpress.org/support/users/ujimoto/)
 * Last activity: [10 years, 7 months ago](https://wordpress.org/support/topic/broken-https-with-pro-version-of-the-plugin/#post-6553246)
 * Status: resolved