Skip to content

Commit

Permalink
Cleaned up readme.txt for 3.2.4.
Browse files Browse the repository at this point in the history
  • Loading branch information
Mike Ems committed Dec 30, 2012
1 parent f15b661 commit 785d121
Showing 1 changed file with 9 additions and 5 deletions.
14 changes: 9 additions & 5 deletions readme.txt
View file
Expand Up @@ -3,21 +3,21 @@ Contributors: Mvied
Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=N9NFVADLVUR7A Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=N9NFVADLVUR7A
Tags: security, encryption, ssl, shared ssl, private ssl, public ssl, private ssl, http, https Tags: security, encryption, ssl, shared ssl, private ssl, public ssl, private ssl, http, https
Requires at least: 3.0 Requires at least: 3.0
Tested up to: 3.4 Tested up to: 3.5
Stable tag: 3.2.3 Stable tag: 3.2.4
License: GPLv3 License: GPLv3


WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites. WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites.


== Description == == Description ==
Read ths basic <a href="http://wordpress.org/extend/plugins/wordpress-https/installation/">Installation Guide</a>. Read the <a href="http://wordpress.org/extend/plugins/wordpress-https/installation/">Installation Guide</a>.
If after setting up the plugin you are experiencing issues, please check the <a href="http://wordpress.org/extend/plugins/wordpress-https/faq/">FAQ</a>. If you are still unable to resolve your issue, <a href="http://wordpress.org/support/plugin/wordpress-https">start a support topic</a> and I will do my best to assist you. If after setting up the plugin you are experiencing issues, please check the <a href="http://wordpress.org/extend/plugins/wordpress-https/faq/">FAQ</a>. If you are still unable to resolve your issue, <a href="http://wordpress.org/support/plugin/wordpress-https">start a support topic</a> and I will do my best to assist you.


== Installation == == Installation ==
1. Upload the `wordpress-https` folder to the `/wp-content/plugins/` directory. 1. Upload the `wordpress-https` folder to the `/wp-content/plugins/` directory.
1. Activate the plugin through the 'Plugins' menu in WordPress. 1. Activate the plugin through the 'Plugins' menu in WordPress.
1. Navigate to the HTTPS settings page in the admin sidebar in the dashboard. 1. Navigate to the HTTPS settings page in the admin sidebar in the dashboard.
1. If you are using a non-default SSL Host for your HTTPS connection (e.g., a subdomain or shared SSL host) enter the entire secure URL into SSL Host. If your installation is located in a folder, you can choose to include it in the URL or not. If you set this to a domain that is not currently serving your WordPress installation over HTTPS and enable Force SSL Admin, you will lock yourself out. Follow instructions in the FAQ to reset the plugin. 1. If you are using a non-default SSL Host for your HTTPS connection (e.g., a subdomain or shared SSL host) enter the entire secure URL into SSL Host. If your installation is located in a folder, you can choose to include it in the URL or not. If you set this to a domain that is not currently serving your WordPress installation over HTTPS and enable Force SSL Admin, you will lock yourself out of your dashboard. Follow instructions in the FAQ to reset the plugin.
1. If you would like connections to your admin panel to be secure, enable Force SSL Admin. If you are using a non-default SSL Host, do not use WordPress' built-in FORCE_SSL_ADMIN or FORCE_SSL_LOGIN. 1. If you would like connections to your admin panel to be secure, enable Force SSL Admin. If you are using a non-default SSL Host, do not use WordPress' built-in FORCE_SSL_ADMIN or FORCE_SSL_LOGIN.
1. If you are looking to secure only your admin panel and/or posts and pages you specify, enable Force SSL Exclusively. This will ensure that any content not specified to be secure is always served over HTTP. 1. If you are looking to secure only your admin panel and/or posts and pages you specify, enable Force SSL Exclusively. This will ensure that any content not specified to be secure is always served over HTTP.
1. You can individually secure post and pages when editing them by updating the settings located in the HTTPS box on the right sidebar. 1. You can individually secure post and pages when editing them by updating the settings located in the HTTPS box on the right sidebar.
Expand All @@ -41,11 +41,14 @@ Once you have identified the insecure elements, you need to figure out what them
</ul> </ul>


= I can't get into my admin panel. How do I fix it? = = I can't get into my admin panel. How do I fix it? =
Since it is possible to lock yourself out of the dasboard, WordPress HTTPS comes with a way to reset the plugin's settings. The plugin makes no permanent changes to WordPress, so this will restore all settings to their defaults. Follow directions under "How do I reset the plugin's settings?"

= How do I reset the plugin's settings? =
Go to /wp-content/plugins/wordpress-https/wordpress-https.php and uncomment (remove the two forward slashes before) the line below, or go to your wp-config.php file and add this line. Hit any page on your site, and then remove it or comment it out again. Go to /wp-content/plugins/wordpress-https/wordpress-https.php and uncomment (remove the two forward slashes before) the line below, or go to your wp-config.php file and add this line. Hit any page on your site, and then remove it or comment it out again.
`define('WPHTTPS_RESET', true);` `define('WPHTTPS_RESET', true);`


= The settings won't save! = = The settings won't save! =
Did you reset the plugin following the steps above and forget to comment the line back out or remove it from wp-config.php? I bet you did. Did you reset the plugin following the steps above and forget to comment the line back out or remove it from wp-config.php?


= How do I make my whole website secure? = = How do I make my whole website secure? =
To make your entire website secure, you simply need to change your site url to use HTTPS instead of HTTP. Please read <a href="http://codex.wordpress.org/Changing_The_Site_URL" target="_blank">how to change the site url</a>. To make your entire website secure, you simply need to change your site url to use HTTPS instead of HTTP. Please read <a href="http://codex.wordpress.org/Changing_The_Site_URL" target="_blank">how to change the site url</a>.
Expand Down Expand Up @@ -91,6 +94,7 @@ add_filter('force_ssl', 'store_force_ssl', 10, 3);`


== Changelog == == Changelog ==
= 3.2.4 = = 3.2.4 =
* Tested with WordPress v3.5.
* Large sites using the default SSL Host (matching the Site URL) should experience a significant performance increase. * Large sites using the default SSL Host (matching the Site URL) should experience a significant performance increase.
* Added the Access-Control-Allow-Origin header to AJAX calls to allow local HTTP pages make HTTPS AJAX calls. * Added the Access-Control-Allow-Origin header to AJAX calls to allow local HTTP pages make HTTPS AJAX calls.
= 3.2.3 = = 3.2.3 =
Expand Down

0 comments on commit 785d121

Please sign in to comment.