Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    When using HTTPS, the following URLs should be HTTPS as well:

    <!-- ngfb header javascript begin -->
    <script type="text/javascript" id="fb-script-header">ngfb_insert_js( "fb-script-header", "http://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.3&appId=1447903715506854" );</script>
    <script type="text/javascript" id="twitter-script-header">ngfb_insert_js( "twitter-script-header", "http://platform.twitter.com/widgets.js" );</script>
    <!-- ngfb header javascript end -->

    Are you using a caching plugin? If so, try disabling it and see if those URLs correct themselves. If they do, then perhaps your caching plugin does not take into account HTTP vs HTTPS.

    NGFB checks the $_SERVER['HTTPS'] variable to know if HTTPS is being used or not. As far as I know, this variable is supported by all web servers.

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Any progress on this?

    js.

    Thread Starter viperouge

    (@viperouge)

    Thank you for your answer.

    It must be the caching (I use W3 total cache), however I wasn’t able to fix it by tweaking the cache plugin settings.. I’m still trying to figure it out 🙂

    Plugin Author JS Morisset

    (@jsmoriss)

    Ah – that would explain it – W3TC is the only plugin I know with consistent bugs in it’s handing of the WP object cache, webpage fragment cache, etc., etc., etc. If you’re using the “fragment cache” feature, try turning it off.

    js.

    Thread Starter viperouge

    (@viperouge)

    Thanks for the followup!
    I just checked and I think I do not have fragment cache active.

    Any other ideas? 🙂

    Plugin Author JS Morisset

    (@jsmoriss)

    Disable W3TC and see if that fixes the issue.

    js.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Serving Social Media JSs through HTTPS’ is closed to new replies.