Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter redkite

    (@redkite)

    Please – someone answer me? The URL for the images (when you click to edit them) is https, but FooGallery’s links are all http.

    Thread Starter redkite

    (@redkite)

    I used this, suggested in another thread, and it made no difference.

    function force_https_the_content($content) {
      if ( is_ssl() )
      {
        $content = str_replace( 'src="https://', 'src="https://', $content );
      }
      return $content;
    }
    add_filter('the_content', 'force_https_the_content');
    Plugin Author bradvin

    (@bradvin)

    Looking at your site – it seems you have solved your problem.

    Just a note that FooGallery uses the core WordPress media library and functions to upload images.

    There are a few options to force HTTPS images I have found:

    Thread Starter redkite

    (@redkite)

    We got the HTTPS working by using a post-processing rule for WP Engine.

    But the biggest problem (taking 2 hours of me chatting with WPE support) was trying to figure out why the thumbnails were being stored in a cache folder. I finally discovered a post about FooGallery stating that this is what you do by default. That was a big mess, maybe you could make it much more obvious that FooGallery is doing this, and how it can be forced to use the actual images instead of cached images.

    WP Engine doesn’t by default backup any folders named /cache/ or /caches/ or /cached/, so when I rolled back to an earlier site version all my FooGallery image thumbnails disappeared. It’s simple to tick the checkbox to force it to use the actual image files, but not if it’s not obvious what that’s for.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Images added with FooGallery don’t use HTTPS’ is closed to new replies.