Certbot with Apache: Difference between revisions
| Line 49: | Line 49: | ||
} | } | ||
$web_site = ' | $web_site = 'WhatEverWebSiteURL'; | ||
$schema = isSecure() ? 'https://' : 'http://'; | $schema = isSecure() ? 'https://' : 'http://'; | ||
$web_site_url = $schema . $web_site; | $web_site_url = $schema . $web_site; | ||
| Line 58: | Line 58: | ||
define( 'FORCE_SSL_LOGIN', true ); | define( 'FORCE_SSL_LOGIN', true ); | ||
define( 'FORCE_SSL_ADMIN', true ); | define( 'FORCE_SSL_ADMIN', true ); | ||
</syntaxhighlight>WordPress makes it hard to switch from HTTP to HTTPS, so try this site to scan for issues: [https://www.whynopadlock.com/results/02d0cc06-1d61- https://www.whynopadlock.com/] | </syntaxhighlight>The last two lines in the above code eliminate the possibility of an administrator or other editor making a mistake (and logging in with HTTP instead of HTTPS) when they login. | ||
WordPress makes it hard to switch from HTTP to HTTPS, so try this site to scan for issues: [https://www.whynopadlock.com/results/02d0cc06-1d61- https://www.whynopadlock.com/] | |||
WordPress Images (especially header images) are tough to change from HTTP to HTTPS, so plugins like this are useful: SSL Insecure Content Fixer (Please note, this plugin may produce a performance hit on websites) | WordPress Images (especially header images) are tough to change from HTTP to HTTPS, so plugins like this are useful: SSL Insecure Content Fixer (Please note, this plugin may produce a performance hit on websites) | ||