After updating site to use SSL all images in posts point to http://
Installing the WordPress HTTPS plugin should take care of it.
Installing the WordPress HTTPS plugin should take care of it.
After a little more reading via the WordPress Codex, I discovered that I was calling the favicon incorrectly. It should be called like this: <link rel=”shortcut icon” href=”https://wordpress.stackexchange.com/questions/240069/<?php echo get_stylesheet_directory_uri(); ?>/favicon.ico” /> Using get_stylesheet_directory_uri() checks for SSL.
try installing this WordPress plugin. http://wordpress.org/extend/plugins/wordpress-https/installation/ but do read the installation instructions as it has some extra things to do after activating the plugin.
I just figured out the issue. You need to add the HTTPS/SSL settings before require_once(ABSPATH . ‘wp-settings.php’); in your wp-config.php So the relevant part of your wp-config.php should look like this. define( ‘FORCE_SSL_ADMIN’, true ); // in some setups HTTP_X_FORWARDED_PROTO might contain // a comma-separated list e.g. http,https // so check for https existence if( … Read more
This is a late answer but this works for me: Change the RewriteCond to this RewriteCond %{HTTP:X-Forwarded-Proto} !https Should be like this: RewriteEngine On RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^(.*)$ https://yourdomain.com/$1 [R,L]
Use the developer tools in Firefox (or Firebug) or Chrome or Safari or IE to see the errors with specific images. 1) You may need to change URLs of media items in the post/page content to https. Search RegEx is a good plugin to be able to search and replace (optionally with grep) through all … Read more
WordPress keeps WP_HOME and WP_SITEURL in DB, this is set during initial installation and usually is the domain of your website, in your case it is a domain with https. Your visiting site via local domain, but WordPress redirects to https live domain, causing redirect loop which obviously fails. To fix this, change WP_HOME and … Read more
There’s not a correct order. Either way will work and results in a WordPress install that is secured with SSL. What makes sense in a situation, depends on the setup and workflow. If you can plan ahead, it’s optimal to set up the SSL on your server first. Because doing so, you don’t have to … Read more
Thanks to @Sorin for posting the trac. From there I found a solution using just filters in functions.php (so no editing the core) Thanks @mensmaximus for posting there: Link: https://core.trac.wordpress.org/ticket/33887#comment:3 <?php add_filter( ‘network_admin_url’, ‘mmx_network_admin_url’, 1, 2 ); function mmx_network_admin_url( $url, $path ){ $url = “https://my_master_domain/wp-admin/network/” . $path; return $url; } add_filter( ‘admin_url’, ‘mmx_admin_url’, 1, 3 … Read more
Yes, you can do this and it does not matter if plugins are different for the two sites, as you are not not using the same tables or anything. Still, if you use plugins that are badly written and build resource urls on top the home url, these will have issues (404 errors mostly).