Assets loaded over insecure http when using https – Themeco Community

Assets loaded over insecure http when using https

pupeno — Mon, 19 Jan 2015 10:38:14 +0000

For a website I’m building we are using https all the time. Unfortunately Theme X is causing a warning since the visual editor is loading some assets over http instead of https leading to mixed content.

My site is at https://screensaver.ninja and if you look at the asset the visual editor is loading over http seems to be this one:

http://screensaverninja.carouselapps.com/wp-content/uploads/sites/2/js_composer/custom.css?ver=4.3.5′ type=’text/css’ media=’screen’ />

How do I fix this?

Reply To: Assets loaded over insecure http when using https

Zeshan — Mon, 19 Jan 2015 19:00:07 +0000

Hi Pupeno,

Thanks for writing in! You could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Cheers!

Reply To: Assets loaded over insecure http when using https

pupeno — Tue, 20 Jan 2015 10:29:58 +0000

I already know which plug in is generating that URL, it’s the WPBakery Visual Composer: https://www.google.co.uk/search?q=”js_composer_custom_css-css”

Reply To: Assets loaded over insecure http when using https

Zeshan — Tue, 20 Jan 2015 15:48:44 +0000

Hi Pupeno,

Thanks for writing in!

Please try installing WordPress HTTPS plugin in your website.

Thanks!

Reply To: Assets loaded over insecure http when using https

pupeno — Tue, 20 Jan 2015 19:04:19 +0000

Hello there,

I added that plug in, but this asset is still requested over http, not https.

Reply To: Assets loaded over insecure http when using https

Rad — Wed, 21 Jan 2015 04:27:53 +0000

Hi there,

I’m not sure why VC will load script that is outside it’s designated domain (eg. screensaver.ninja vs screensaverninja.carouselapps.com ).

Could be that your staging server or your cdn server. No matter which the reason, the url/path should be updated too. As there is no way js composer could transfer its file somewhere else, or upload to cdn hosting, or change its own url as it’s only re-using the plugin_url() given by wordpress.

http://codex.wordpress.org/Function_Reference/plugins_url

In plugin and theme development, developer must not to use static url. So when user decided to change their site’s url, it will just adapt to current url which includes http and https protocols.

All I could guess is cache or non-updated cdn. Would you mind providing your admin login in private for a closer look?

Thanks!

Reply To: Assets loaded over insecure http when using https

pupeno — Thu, 22 Jan 2015 11:23:37 +0000

Hello,

screensaver.ninja is hosted as part of a network of sites at carouselapps.com. It’s canonical name is screensaverninja.carouselapps.com and screensaver.ninja is mapped to it, so, it’s perfectly fine (and expected) for assets to be loaded from screensaverninja.carouselapps.com.

I looked at the Visual Editor source code, which led me to look at the options table in my database. I changed baseurl and home to be https:// instead of http:// and that helped resolve most of the issues. I’m still getting this one:

GET http://theme.co/x/demo/integrity/1/wp-content/uploads/sites/2/2013/06/bg-integrity-1.png

but I’m not sure why it’s using http. The mention in the HTML of the site is correct:

background:#f3f3f3 url(//theme.co/x/demo/integrity/1/wp-content/uploads/sites/2/2013/06/bg-integrity-1.png) center top repeat;

Reply To: Assets loaded over insecure http when using https

pupeno — Thu, 22 Jan 2015 11:41:29 +0000

I found why it’s being loaded over http instead of https. There’s a redirect from:

https://theme.co/x/demo/integrity/1/wp-content/uploads/sites/2/2013/06/bg-integrity-1.png

http://theme.co/x/demo/integrity/1/wp-content/uploads/sites/2/2013/06/bg-integrity-1.png

Now, I’m trying to figure out how to avoid loading that altogether as I don’t need it.

Reply To: Assets loaded over insecure http when using https

pupeno — Thu, 22 Jan 2015 11:50:03 +0000

I set and removed background pattern for body, and the problem went away. Now it’s fully working over https.

Reply To: Assets loaded over insecure http when using https

Rad — Thu, 22 Jan 2015 21:58:21 +0000

Okay, great to hear that. Or you can download that image and host it at your site 🙂