https and blocked content

  • Unknown's avatar

    Ever since I clicked the box to use https on my admin pages, I have had security warnings galore. Did follow the directions for turning them off that is posted on WordPress, but it hasn’t made a difference (in fact, it’s added a new level of security boxes that ask if it’s ok to go to my trusted site). Is anyone else having this problem? Anyone know how to fix it?

    (I tried unclicking the box–though I must admit I’m confused about whether or not my home computer is considered a “public connection” and if it needs to be on and I’m afraid not to use the https connection–and the security warnings STILL happened, so I reclicked it to be on again.)

    Help???

  • Unknown's avatar

    In the comments in the announcement, Heather addressed this:

    Heather
    September 17th, 2008 at 12:23 am

    If you’re using Internet Explorer, you can turn off those warnings by following these steps:

    1) Add *.wordpress.com to your list of trusted sites under the Security tab.
    2) Set Internet Options> Security> Trusted Sites> Custom Level> Miscellaneous> Display Mixed Content to “Enable.”

  • Unknown's avatar

    Thank you, yes. I did all that, and I am still getting the warnings.

  • Unknown's avatar

    I suspect you are using IE, and if you are on Vista, well it’s warning crazy. You might think of trying Firefox 3 to work with WordPress and see how that works for you.

  • Unknown's avatar

    Thanks very much for the suggestion.

  • Unknown's avatar

    From another thread, it appears like IE6 doesn’t respond to the above settings and continues to pop up warnings. No idea how to stop it.

  • Unknown's avatar

    I too am having that problem with IE7 on XP and it is driving me crazy as well. I tried to unchecl the SSL requirement in my profile, but no change and the url continues to open at a https.

  • Unknown's avatar

    Log out, clear your browser cache and cookies, restart your browser and then log back in. That will clear things for you.

  • The topic ‘https and blocked content’ is closed to new replies.