Yes – entirely possible to use SSL on only 1 site in a WP network. In the past, we have done this using .htaccess to force HTTPS for all URLs of a particular site, leaving all others HTTP. This was done using carefully written Apache URL rewrites. The SSL used was a wildcard cert although … Read more
Remove all of the force SSL plugins that you’re running, revert back to your default settings in the wp-config.php and .htaccess before applying forces to use HTTPS. This will remove all of the conflicts you are having and the redirect loops. After that, follow these steps: Go and download Interconnect IT’s Database Search & Replace … Read more
I think the simpler solution would be to create your own function: function get_theme_mod_img($mod_name){ return str_replace(array(‘http:’, ‘https:’), ”, get_theme_mod($mod_name)); } then just use it: <a href=”https://wordpress.stackexchange.com/questions/256864/<?php echo esc_url(get_theme_mod(“slide_one_link’)); ?>”><img src=”<?php echo esc_url( get_theme_mod_img( ‘slide_img_upload_one’ ) ); ?>” alt=”<?php echo get_theme_mod( ‘slide_title_1’ ); ?>” /></a> there is another solution that involve filters as you can see … Read more
Check two things: in the wp-options table, the site URLs (in two places) should be the full URL, as in https://www.example.com . check the site’s htaccess file for proper rewrite of http to https. For a htaccess rule, this one works in most case: RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] Then look … Read more
If you are using custom front-end registration through wp_signon function, check, if the second parameter, passed to that function is true: $user_signon = wp_signon( $info, true ); ). The second parameter tells WordPress to set the secure cookie for login. It works fine with SSL.
Got it solved. Turns out the server was hosted behind a reversed proxy, causing WordPress not knowing it was running over https. Once I knew this, I found the solutions in the official documentation: http://codex.wordpress.org/Administration_Over_SSL (under “Using a Reverse Proxy”) This was needed in my wp-config. define(‘FORCE_SSL_ADMIN’, true); if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’] == ‘https’) $_SERVER[‘HTTPS’]=’on’
e.g. wpinstance.com/wp-admin is not rewritten into wp-admin/ with a trailing slash, but into ugly long link: https://wpinstance.com/wp-login.php?redirect_to=https%3A%2F%2Fwpinstance.com%2Fwp-admin%2F&reauth=1 As is already mentioned in comments, this is intentional. There is no “pretty” URL for this. And neither does there need to be – this should not be indexed or linked to. do I need .htaccess? No, you … Read more
First, rename the folder wp-content/plugins/wordpress-https to wp-content/plugins/wordpress-https-OFF so that WordPress can’t find it to run it. Second, add the following lines to your wp-config.php file, replacing the domain name with your domain name: define( ‘WP_SITEURL’, ‘http://example.com/’ ); define( ‘WP_HOME’, ‘http://example.com/’ );
I had exactly the same problem and the solution for me was to add these lines to /etc/apache2/sites-enabled/default-ssl.conf, which is my SSL-enabled website’s configuration file: <Directory /var/www/html/> AllowOverride All </Directory> Of course, this assumes DocumentRoot /var/www/html. Change accordingly if is this is different in your setup. The thing is that WordPress uses .htaccess rules to … Read more
The code you provided could cause issues with 3rd party URLs in hyperlinks not running https. You can fix this by including your home url, e.g: $content = str_replace( set_url_scheme( home_url(), ‘http’ ), set_url_scheme( home_url(), ‘relative’ ), $content); Next, you’re applying this when you’d like to display the content, which means you need to do … Read more