Plugin load order

G’day Birmania,

You haven’t posted a link to your website, so I can’t see what’s not being fixed. I’ll just have to guess ??

The only thing that should be affected by order of loading plugins is the proxy fix. You can easily implement that in your wp-config.php to get in front of anything WordPress loads, so there’s no need to modify the load order of plugins.

e.g. for CloudFlare, you should be able to use the HTTP_X_FORWARDED_PROTO fix by adding this to your wp-config.php file before any mention of ABSPATH:

if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
    $_SERVER['HTTPS'] = 'on';
}

cheers,
Ross

Hi Webaware,

Sorry that I didn’t put my website URL. I was thinking that it will not be really relevant for your analysis.
=> Just a mixed content error on a plugin’s URL that is generated from PHP.

Indeed, my mixed content error came from All-In-One-Event-Calendar plugin which is computing some URL when plugin is included, with the following line of code :
$ai1ec_base_url = plugins_url( ”, __FILE__ );
=> This line will produce an “HTTP” URL when plugin is included before “SSL Insecure Content Fixer” and “HTTPS” if included after.

However, your proxy fix is the perfect trick, it works like a charm.
Moreover, it solve all mixed content problems, even with “SSL Insecure Content Fixer” desactivated.

I hope that it is a normal behavior… !

And if you need to take a look : Website

Thanks a lot Ross,
Do not hesitate to indicate if I did a mistake by desactivating your plugin.

Yours faithfully,
Birmania

G’day Birmania,

Excellent, and it sounds like everything else is OK so you don’t need my plugin. That’s the best solution then!

I haven’t examined your website, but if you do find some mixed content, just enable my plugin again and test with the different options.

cheers,
Ross