Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Stats Page https issue...

    Feathercoin Discussion
    1
    3
    945
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mnstrcck last edited by

      Thought I’d throw this up:

      oRaKJhR.png

      YaZTiqL.png

      Using Chrome 35.0.1916.114 on OS X - https only issue.

      1 Reply Last reply Reply Quote 0
      • M
        mnstrcck last edited by

        IawgoM,

        Thanks - I did a bit of reading, and it looks like a Chrome specific issue with how the fonts are called on in the .css

        I am bringing it up not just for myself, but for other users visiting the site with my setup.

        From: https://yoast.com/wordpress-ssl-setup/

        "Broken SSL: fixing links in theme files

        If you load a page over SSL, all the other files that are loaded on that page should also be loaded over SSL for it to not be “broken”. This means that every single image, javascript file, stylesheet etc. needs to be loaded over SSL. WordPress will fix a lot of this for you, but you’ll probably encounter some issues, as did I, causing a broken SSL icon in the location bar, as shown above here.

        In my case, within my theme’s stylesheet, I was loading a google web font file. That shouldn’t be an issue, of course, but I was loading that font file over http, instead of using what’s called a protocol relative link. Every time you’re embedding images, javascript or CSS files, you should be using a protocol relative link. Instead of linking to:

        http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,600

        I’m now linking to:

        //fonts.googleapis.com/css?family=Source+Sans+Pro:400,600

        As you can see, I left out the http:, this will make the browser use the current protocol to fetch that file. This means that when a user is on plain http, it’ll use that, which is faster, but if the user is on https, it’ll use the safe https link."

        Might be a good idea to update the .css files

        Let me know what you think!

        1 Reply Last reply Reply Quote 0
        • M
          mnstrcck last edited by

          Thanks! I’ll look into this after I get back from my vacation :)

          :D :D

          1 Reply Last reply Reply Quote 0
          • First post
            Last post