• Resolved kosnathaniel

    (@kosnathaniel)


    When the Breeze plugin is enabled, I encounter the following error: “Mixed Content: The page at ‘https:// .org/’ was loaded over HTTPS, but requested an insecure stylesheet ‘https:// .org/wp-content/uploads/sites/3/breeze/google/fonts/playfair_display_sc/playfair_display_sc.css’. This request has been blocked; the content must be served over HTTPS.”

    I tried disabling all plugins on the site and reenabling them one by one. I had no issues until I enabled the Breeze Plugin. I then disabled it and enabled all the other plugins with no issues. I enabled the breeze plugin again, and the issue reappeared.

    The site is a multi-site network and it affects the entire network with the same issue.

    • This topic was modified 7 months, 2 weeks ago by kosnathaniel.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author owaisalam

    (@owaisalam)

    If you are able to serve CSS, JavaScript, and other assets over HTTPS, the most effective approach is to use // as the scheme for your asset URLs.

    This practice is known as “protocol-relative URLs.” By using // instead of explicitly specifying https:// or https://, the browser automatically uses the same protocol as the parent document. For example, if the page is loaded over HTTPS, the assets will also be served over HTTPS.

    This method not only simplifies the URL management but also helps avoid potential security warnings and mixed content issues that can arise when loading assets over HTTP on an HTTPS page. Here’s an example of how it works:

    <link rel="stylesheet" href="https://your-domain/styles.css">
    <script src="https://your-domain/app.js"></script>

    @owaisalam The issue is Breeze itself is causing this issue because it happens when you allow breeze to cache Google Fonts. Those fonts are tried to load over http instead of https: https://prnt.sc/KrOyT8xEuVmm

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.