Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Where can I see the site? What plugins and theme do you use?

    Normally it should consider the current scheme (http or https) and output correct URL in <link> elements.

    Thread Starter stepfret

    (@stepfret)

    Hi Takayuki — Thanks for responding.

    This is the site: https://motorthrust.com/.

    Our theme is Just Landed.

    Our plugins:

    CallRail Phone Call Tracking
    Contact Form 7
    Facebook Pixel Conversions for WordPress
    Force SSL URL Scheme
    Insert Headers and Footers
    Instapage WordPress plugin
    LeadPages Connector
    Limit Login Attempts
    MailChimp for WordPress Lite
    Rename wp-login.php
    UpdraftPlus – Backup/Restore
    URL Params
    WordPress Importer

    I have reactivated Contact Form 7 so you can see the issue, but I can’t leave it like that for long as people using IE get a warning about insecure content at the bottom of the page.

    Both the WordPress Address and Site Address in general settings start with “https”.

    These are the resources the Chrome Console lists as causing the mixed content warnings:

    http://motorthrust.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=4.1

    http://motorthrust.com/wp-content/plugins/contact-form-7/includes/js/jquery.form.min.js?ver=3.51.0-2014.06.20

    http://motorthrust.com/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=4.1

    Thanks,
    Josh

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    The page seems cache enabled. Which plugin does the caching?

    What if you deactivate all of the plugins and switch to the default theme?

    Thread Starter stepfret

    (@stepfret)

    Hi Takayuki — There is no caching enabled that I’m aware of. We even disabled Varnish on the server a few days ago.

    I just disabled all plugins except Contact Form 7 and the Force SSL, which is obviously needed to test this issue.

    I also changed the theme to 2013.

    I resaved the permalinks.

    I cleared IE’s cookies and cache then refreshed the page. Still getting the same warnings.

    I’ll leave it like that for a short period of time so you can see it, but then I obviously need to switch it back.

    Thanks,
    Josh

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Thank you. The page seems still “cached” (I’m looking at the _wpcf7 JavaScript variable in the footer in the HTML source). Any chance do you have a line in wp-config.php that defines WP_CACHE constant?

    Thread Starter stepfret

    (@stepfret)

    Yes, I found define(‘WP_CACHE’, true); Added by W3 Total Cache.

    We probably had that installed at one point or another.

    I have commented out that line in wp-config.php now.

    It didn’t seem to change anything. Is there an extra step I would need to take now?

    Thanks,
    Josh

    Thread Starter stepfret

    (@stepfret)

    OK, I have to put the site back together now. Let me know when you can next take a look at it.

    Thanks for your help so far,
    Josh

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    If you have remains of a plugin that is previously used, it’s possible that you have other remains. Check the wp-config.php again, do you find other constant definitions that are not found in other sites? Such as, WPCF7_PLUGIN_URL?

    Also, check the .htaccess file in the top level directory. If it looks strange, try removing and regenerating it in the Settings > Permalinks admin menu.

    Thread Starter stepfret

    (@stepfret)

    Hi Takayuki — Nothing seems out of place in wp-config.php or .htaccess.

    I’ve looked through the plugins folder and other areas and don’t see any remnants of caching.

    The only thing I can get to fix the situation is activating the WP HTTPS plugin, which I’d rather not do since nothing else on the site needs it.

    Do you have any other ideas?

    Thanks,
    Josh

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    I’m still not sure what is causing this, but I guess it’s better to double-check in the https-ize process.

    Can you test the development version that you can download from here (Other Versions > Development Version)? If this solves the issue, I’ll include it in the next release.

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

The topic ‘resources loaded without https’ is closed to new replies.