G’day Henry,
That’s all coming from Visual Composer, which is a premium (paid) plugin. You should harass the author of that plugin — it has come up here before, in other people’s support tickets. You’ve paid them for support, so go get it.
Please let me know what response you get. I’m keen to know how the plugin author is dealing with this issue, if at all.
cheers,
Ross
how is that causing the problem exactly and how is it preventing insecure content fixer from removing the mixed content?
if the issue has come up before how did the other guy solve it.
I would also like to know that
All seem to be coming from this file:
https://sleepsharestay.com/wp-content/uploads/js_composer/js_composer_front_custom.css
That’s a generated file created by Visual Composer, which is a premium (not-free) plugin so I can’t download and examine it.
It’s possible that if you edit your Visual Composer settings from the WordPress admin while in https, it will fix that generated file. However, I strongly suggest you take this up with the plugin author, since you would have paid to get this plugin and support from them.
As to “the other guy”, none of the other people who raised issues with that plugin responded further once I told them where the problem was. I can’t even tell you whether they solved their problems.
cheers,
Ross
Just got word from visual composer plugin authors.And here is what they are saying:
” This is not a theme issue, it is related to the server setting which is mostly unable to set a protocol on the css which handles design options. Kindly check.”
How do you crack this?
G’day Henry,
If you visit the Tools > SSL Tests page in the WordPress admin, you can check to see how HTTPS Detection is working. The plugin’s settings page at Settings > SSL Insecure Content will show you what setting you have for HTTPS Detection, as explained here:
https://ssl.webaware.net.au/https-detection/
But I can tell you now that WordPress is detecting HTTPS just fine, because everything is loading on HTTPS except for those Visual Composer scripts.
Did you try logging in to your admin with HTTPS and saving your Visual Composer settings, as I suggested above?
cheers,
Ross
i have tried doing that and its not just working
I know what ssl insecure content fixer does is to try and create relative paths for the absolute urls,is there a way of coding that maybe?..
Or how exactly can i trace the url being generated by visual composer and change it to https?.
How does one even find links and paths in wordpress?
G’day Henry,
The answer to your last question is, “It depends”. There are so many ways. For Visual Composer, I’d imagine that it is storing some settings in the options table, and these settings are stored with http: protocol.
The reason this plugin isn’t fixing Visual Composer’s stylesheet is that it’s stored externally as a file in the uploads folder, and this plugin only fixes things in the page HTML.
Really, your best bet is to get the plugin author to provide support. You bought it, they support it (at least, that’s the theory).
cheers,
Ross
So if i want to work around this,while checking the vc files,do i go for the php files or the js files?
G’day Henry,
It’ll be in the PHP files. Look for where it generates the file “js_composer_front_custom.css”, that’s where the fix is required.
cheers,
Ross
Ross,an update on the visual composer plugin fixed most of the errors.
Two however are remaining:
Mixed Content: The page at ‘https://sleepsharestay.com/’ was loaded over HTTPS, but requested an insecure image ‘http://demo1.wpresidence.net/wp-content/uploads/2014/05/map1.jpg’. This content should also be served over HTTPS.
GET https://www.ssl.com/images/ssl_seal_1.png net::ERR_NAME_NOT_RESOLVED
How can those two be fixed?
G’day Henry,
map1.jpg is a background image on a Revolution Slider panel. Look at your Revolution Slider settings for that one.
The “name not resolved” error was probably a temporary problem with DNS for http://www.ssl.com, as I don’t see that problem.
cheers,
Ross
