This is somewhat of a guess, but it is probably a result of the web server configuration. What your server probably does is to see that the request want to load the blog url of the site. It checks out and sees that blog is a directory adds a slash and redirects to it. Now … Read more
I also had this experience with chrome and firefox, they switch http to https and did not find a way to overcome it, so i used internet explorer in that windows machine. I don’t think you can have ssl on localhost or an ip address, i guess you know it as you used devfoo.pro. SSL … Read more
By default web servers / your hosting serves files from HTTPS from a separate folder. This means that there are actually two directories on the server for hosting your website files: For example public_html – the standard “public” folder for HTTP requests private_html – the standard “private” folder for HTTPS requests (e.g. secure content) I … Read more
RewriteCond %{HTTP_HOST} ^example\.me [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.example.me/$1 [R,L] You’ve not stated where exactly you are adding these rules in your .htaccess file(s). The order is important. These directives need to go at the top of the .htaccess file, before the WordPress front-controller, otherwise they won’t redirect anything other than static resources. This … Read more
You can use the define(‘FORCE_SSL_LOGIN’, true); options provided by WP. You just have to add the line in wp-config.php. Here is the link to wordpress codex, in case that you need more examples.
this may be called as a bug in get_permalink, but it may not be. I had the same case, and when I tried to echo site_url(); I get the https://… But once I updated the options for siteurl and home to have https get_option( ‘siteurl’ ); get_option( ‘home’ ); get_permalink worked fine. I noticed that … 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
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’
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/’ );