Return to previous page

Classico 1.5 – https broken due to Google Font Api

This topic has 6 replies, 3 voices, and was last updated 8 years, 11 months ago ago by Jack Richardson

Robert

Participant

February 27, 2016 at 06:19
I am using an SSL certificate for my site. However, despite trying to change any instances of http:// to // I find in the code for Classico, I still get an error relating to Google fonts:

Mixed Content: The page at 'https://www.mydomain.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Open+Sans:400,600'. This request has been blocked; the content must be served over HTTPS. plugins.min.js:5 Uncaught TypeError: Cannot read property 'width' of undefined

I order to fix the error, I changed the file themes/classico/framework/shortcodes.php
I changed the lines relating to https://fonts.googleapis.com to //fonts.googleapis.com.

This has still not fixed the problem and the error persists. Please advise?

Note the 2nd (unrelated) error underneath with regards to the plugins.min.js:5. Looks like a coding error that the developers need to look at. Please comment?
#115132 Copied Theme version: 1.5
5 Answers

Eva Kemp

Support staff

February 27, 2016 at 10:44

Hello,

Please provide your site name and FTP/WP admin panel credentials in Private Content.

Thank you.
Regards,
Eva Kemp.

#115160 Copied
Robert

Participant

February 27, 2016 at 15:36
Hi Eva.

Of the two errors, I have found the source of the first, “Mixed Content” error. I was certain after searching everywhere in the theme folder that the theme files did not create this problem. So I disabled all the plugins and added them back one-by-one, whilst observing the Google Chrome Developer COnsole (F12) and refreshing a tab in Google Chrome that showed the error each time.

The plugin that caused the problem was one I added, “Woocommerce LightBox”. Within the pluligin folder was this offending file:

/plugins/woocommerce-lightbox/assets/css/main.css

The following line caused the issue:-

/** * Woocommerce Lighbox by WpBean */ @import url(http://fonts.googleapis.com/css?family=Open+Sans:400,600);

Not sure why an official Woocommerce plugin would have this problem in it, considering with ecommerce sites nowadays, its preferable to have an SSL certificate. Anyway, I stripped out the reference to http: just leaving the //.

Hope this helps others.

What remains to be solved is the second error:

Uncaught TypeError: Cannot read property 'width' of undefined plugins.min.js.5

This error also exists on your demo site, so its not anything to do with something I’ve changed or an extra plugin you don’t have on the demo.

https://www.8theme.com/demo/classico/variant1/

If you visit the demo link above in Google Chrome, then press F12 to view the Google Chrome Developer Console, you’ll see the error marked in red. No need for my site to see this.

Please take a look and explain what is causing this please? Looks to me like a coding error.
#115179 Copied
Jack Richardson

Support staff

March 1, 2016 at 09:49

Hello,

Our demo site uses old theme version. When we tested the latest theme version there wasn’t any error. Are you using Classico 1.5 version and all updated plugins?

Best regards,
Jack Richardson.

#115569 Copied

Robert

Participant

March 1, 2016 at 10:11

Yes, am using Classico v1.5. Still getting the error using the Google Chrome… press F12… click Security tab to see the error. Please comment that you looked in the ‘Security’ tab. The error is still showing on your demo page, so where exactly did you test? Can I see?

I have replicated this error on two different servers with default Classico demo install v1.5 so far.

The error relates to this file on your demo…

https://www.8theme.com/demo/classico/variant1/wp-content/themes/classico/js/plugins.min.js

This file has the same error in Classico v1.5. This is not related to any additional plugin that can be updated.

#115587 Copied

Jack Richardson

Support staff

March 2, 2016 at 11:06

Hello,

I’ve sent archive with fixed .js files to your contact email address. You need to replace original .js files with the provided ones in the wp-content/themes/classico/js folder.

Best regards,
Jack Richardson.

#115792 Copied
Viewing 6 results - 1 through 6 (of 6 total)

The issue related to '‘Classico 1.5 – https broken due to Google Font Api’' has been successfully resolved, and the topic is now closed for further responses

Classico 1.5 – https broken due to Google Font Api

Recent Topics

Helpful Topics

Useful links WooCommerce & WordPress

Browse by popular tags:

Explore our best WordPress WooCommerce Themes collection