FooGallery calling insecure CSS after 2.1.33 update

Hi @fmgguy

Please enable the setting “force HTTPS” on the FooGallery settings page.

For some installs, the path to your css file returns a non secure path. This setting forces it to always be secure. The reason it is showing now is because the update clears the css cache.

Let us know how that goes?

Thanks for the quick response!

I have checked the “force HTTPS” checkbox, but the error persists (even after clearing the Thumbnail cache, and my browser cache). I was able to get the home page displaying correctly by copying the insecure CSS into the custom css textarea, but that just is a temporary fix. Any other ideas?

Just as an FYI, I am using FooGallery on other sites and not seeing this issue on them.

Hi @fmgguy

I’m sorry to learn that you are going through this issue and I’ll be happy to help.

First, this is more of a site issue than a FooGallery issue, and that’s why you are not seeing it happen on your other sites as you mentioned. I’ve also observed that the Masonry gallery is displaying the images in 3 columns too, just as you configured it.

Secondly, just to confirm, I’d like to start with the basics and kindly ask you to log in to your dashboard and navigate to Settings -> General and confirm if the WordPress Address (URL) and Site Address (URL) values both use HTTPS as the prefix.

Kindly update us on this. Thanks.

Kind regards,
Elvis.

Thank you. Yes, both the WP address and site address are setup with https.

Hi @fmgguy

What exactly is causing this is really tough for me to figure out from my end, so I’m going to share with you a guide with a couple of solutions that I’d like you to kindly try from your end and let me know which one, if any, does work for you: How To Fix Mixed Content Errors

Kindly try this and let me know how it goes.

Kind regards,
Elvis.

Thank you for that info. I was able to fix the issue using a plugin (SSL Insecure Content Fixer). It’s not ideal, but it’s fixed.

Thanks again for your help!