You can’t hook is_ssl() to override the result, and as you’ve noticed you can’t edit WordPress Core itself or your changes will get lost if you’re using built-in automatic updates. So the usual approach – see the WordPress documentation – is to set $_SERVER[‘HTTPS’] = ‘on’;, which is the property is_ssl() tests. Add the following … Read more
You have alot of mixed content warnings, be sure to change your scripts and images to call https. For example if you can find the reference the following URL in your theme http://api-idx.diversesolutions.com/Styles/Libraries/juicebox/theme.css Replace it with: https://api-idx.diversesolutions.com/Styles/Libraries/juicebox/theme.css which will work because the provider has a valid SSL certificate. But I would highly recommend physically searching … Read more
The https change was not the cause. Actually – coincidentally – the W3 Total Cache was updated on the same day, and the Minify setting was breaking lines between meta and property words on the HTML, which were causing the error on Facebook debug tool.
You have “www.wisconsinwetlands.org” URLs redirecting to insecure “http://wisconsinwetlands.org“. The cases you have used these is in the images on the page. Every image that is set as “https://www.” redirects to the insecure version. So while you do need to fix that and correctly configure your setup so that both “www” and non-www URLs are secure, … Read more
Adding this to my theme’s functions.php solved this same problem for me: add_filter( ‘wp_image_editors’, ‘change_graphic_lib’ ); function change_graphic_lib($array) { return array( ‘WP_Image_Editor_GD’, ‘WP_Image_Editor_Imagick’ ); }
WordPress forces HTTPS to HTTP in template
Domain Mapping for WordPress MU and https redirection – How to?
The title and last line of your question conflict, in the title you want HTTPS as the end result, in the final line your asking for HTTP. I assume the title is correct. Don’t use a WP plugin for this. I don’t have a godaddy account, but most commonly you would want an .htaccess file … Read more
The root of my problem was none of the above and it was a change in the way WordPress internal variables worked. The plug-in I was attempting to troubleshoot was utilizing the following: define(‘WPA_PLUGIN_DIR’, WP_PLUGIN_DIR . “https://wordpress.stackexchange.com/” . WPA_PLUGIN_NAME); define(‘WPA_PLUGIN_URL’, WP_PLUGIN_URL . “https://wordpress.stackexchange.com/” . WPA_PLUGIN_NAME); New Code which per these two links stating to do … Read more
You have to modify either before # BEGIN WordPress or after # END WordPress. This part is modified by WP, once you change your permanlink