Skip to content
100644 205 lines (188 sloc) 13.7 KB
10685d9 @mvied Version 2.0.3
1 === WordPress HTTPS (SSL) ===
2 Contributors: Mvied
3 Donate link:
4 Tags: security, encryption, ssl, shared ssl, private ssl, public ssl, private ssl, http, https
5 Requires at least: 2.7.0
6 Tested up to: 3.3
cd6ec9d @mvied Added stable tag to readme.txt.
7 Stable tag: 2.0.3
10685d9 @mvied Version 2.0.3
9 WordPress HTTPS is intended to be an all-in-one solution to using SSL on WordPress sites.
11 == Description ==
12 <ul>
13 <li>Supports Shared and Private SSL.</li>
14 <li>Helps reduce or completely fix partially encrypted / mixed content errors.</li>
15 <li>Force SSL on a per-page basis.</li>
16 <li>Force SSL in admin panel.</li>
17 </ul>
19 If you're having partially encrypted/mixed content errors or other problems, please read the <a href="">FAQ</a>. If you're still having trouble, please <a href="">start a support topic</a> and I will do my best to assist you.
21 == Installation ==
22 1. Upload the `wordpress-https` folder to the `/wp-content/plugins/` directory.
23 1. Activate the plugin through the 'Plugins' menu in WordPress.
25 == Frequently Asked Questions ==
26 = How do I make my whole website secure? =
27 To make your entire website secure, you simply need to change your home url and site url to use HTTPS instead of HTTP. Please read <a href="" target="_blank">how to change the site url</a>.
29 = How do I make only certain pages secure? =
30 In the Publish box on the add/edit post screen, a checkbox for 'Force SSL' has been added to make this process easy. See Screenshots if you're having a hard time finding it.
32 = I changed my SSL Host and now I can't get into my admin panel! =
33 Go to your wp-config.php file and add this line. Hit any page on your site, and then remove it.
34 `define('WPHTTPS_RESET', true);`
36 = I'm getting 404 errors on all of my pages. Why? =
37 If you're using a public/shared SSL, try disabling your custom permalink structure. Some public/shared SSL's have issues with WordPress' permalinks because of the way they are configured.
39 = How do I fix partially encrypted/mixed content errors? =
40 To identify what is causing your page(s) to be insecure, please follow the instructions below.
41 <ol>
42 <li>Download <a href="" target="_blank">Google Chrome</a>.</li>
43 <li>Open the page you're having trouble with in Google Chrome.</li>
44 <li>Open the Developer Tools. <a href="" target="_blank">How to access the Developer Tools.</a></li>
45 <li>Click on the Console tab.</li>
46 </ol>
47 For each item that is making your page partially encrypted, you should see an entry in the console similar to "The page at displayed insecure content from" Note that the URL that is loading insecure content is HTTP and not HTTPS.
49 Most insecure content warnings can generally be resolved by changing absolute references to elements, or removing the insecure elements from the page completely. Although WordPress HTTPS does its best to fix all insecure content, there are a few cases that are impossible to fix.
50 <ul>
51 <li>Elements loaded via JavaScript that are hard-coded to HTTP. Usually this can be fixed by altering the JavaScript calling these elements.</li>
52 <li>External elements that can not be delivered over HTTPS. These elements will have to be removed from the page, or hosted locally so that they can be loaded over HTTPS.</li>
53 <li>YouTube videos - YouTube does not allow videos to be streamed over HTTPS. YouTube videos will have to be removed from secure pages.</li>
54 <li>Google Maps - Loading Google maps over HTTPS requires a Google Maps API Premiere account. (<a href="" target="_blank">source</a>)</li>
55 </ul>
57 = Is there a hook or filter to force pages to be secure? =
59 Yes! Here is an example of how to use the 'force_ssl' hook to force a page to be secure.
60 `function custom_force_ssl( $force_ssl, $post_id ) {
61 if ( $post_id == 5 ) {
62 return true
63 }
64 return $force_ssl;
65 }
67 add_filter('force_ssl' , 'custom_force_ssl', 10, 2);`
69 == Screenshots ==
70 1. WordPress HTTPS Settings screen
71 2. Force SSL checkbox added to add/edit posts screen
73 == Changelog ==
e30d8fd @mvied Updated with 2.0.4 change log.
74 = 2.0.4 =
75 * Bug Fix - Users using Shared SSL should no longer have broken URL's and redirects.
76 * Bug Fix - Pages should correctly be identified as HTTPS if PHP returns an IP address for SERVER_ADDR in $_SERVER.
77 * Bug Fix - Users using the default permalink structure should now have URL's being properly changed to/from HTTPS.
10685d9 @mvied Version 2.0.3
78 = 2.0.3 =
79 * Force SSL Admin will always be enabled when FORCE_SSL_ADMIN is true in wp-config.php.
80 * Bug Fix - Users using Shared SSL should no longer have issues with the SSL Host path duplicating in URL's.
81 * Bug Fix - The plugin should now function properly when using a subdomain as the SSL Host.
82 * Bug Fix - Page and post links will only be forced to HTTPS when using a different SSL Host that is not a subdomain of your Home URL.
83 * Bug Fix - WordPress HTTPS should no longer generate erroneous notices and warnings in apache error logs. (If I missed any, let me know)
84 = 2.0.2 =
85 * Bug Fix - SSL Host option was not being saved correctly upon subsequent saves. This was causing redirect loops for most users.
86 = 2.0.1 =
87 * Ensured that deprected options are removed from a WordPress installation when activating the plugin.
88 * Added a button to the WordPress HTTPS settings page to reset all plugin settings and cache.
89 * Bug Fix - URL's entered for SSL Host were not validing correctly.
90 * Bug Fix - External URL's were not always being identified as valid external elements.
91 * Bug Fix - Slight enhancement to SSL detection.
92 = 2.0 =
93 * Full support for using a custom SSL port has been added. A special thanks to <a href="">Chris "doingweb" Antes</a> for his feedback and testing of this feature.
94 * Forcing pages to/from HTTPS is now pluggable using the 'force_ssl' filter.
95 * When using Force Shared SSL Admin, links to the admin panel will always be rewritten with the Shared SSL Host.
96 * When using Shared SSL, all links to post and pages from within the admin panel will use the Shared SSL Host to retain administration functionality on those pages.
97 * Redirects to the admin panel now hook into wp_redirect rather than using the auth_redirect pluggable function.
98 * Canonical redirects will now still occur on sites usinga different SSL Host, but not on secure pages.
99 * Cookies are now set with hooks rather than pluggable functions.
100 * Plugin will now delete all options and custom metadata when uninstalled.
101 * Added a HTTP_X_FORWARDED_PROTO check to the is_ssl function.
102 * Internal HTTPS Elements option has been removed. Disabling this option was never a good idea, so it was removed and the plugin will always act as it did when this option was enabled.
103 * External HTTPS Elements option has been removed. The handling of external elements has improved in such a way that this option is no longer required.
104 * Disable Automatic HTTPS option has been removed. This option should have generally been enabled anyway.
105 * Bug Fix - After logging in, the logged_in cookie was not being set properly. This caused the admin bar to not show up in both HTTP and HTTPS.
106 * Bug Fix - When using Shared SSL, the login page would not honor the redirect_to variable after a successful login.
107 = 1.9.2 =
108 * Added External URL caching to the plugin so that external elements will only be checked for once, increasing the speed of sites not using the Bypass External Check option.
109 * Any forms whose action points to page that has the Forced SSL option on will be updated to HTTPS even on HTTP pages.
110 * Bug Fix - When using Shared SSL, permalink structure was being buggy.
111 * Bug Fix - Certain server configurations were causing the plugin to create redirect loops when using the Force SSL Exclusively option.
112 = 1.9.1 =
113 * Bug Fix - Cookies were not being set to the correct paths when logging in, causing logins to fail.
114 * Bug Fix - Links to the front page when using latest posts were not correctly being set to HTTP/HTTPS.
115 * Bug Fix - When using Shared SSL, the HTTPS version of the site_url was not being correctly replaced with the Shared SSL URL for internal elements.
116 * Bug Fix - When using Shared SSL, the admin login page was not always redirecting properly due to output buffering.
117 * Bug Fix - When using Shared SSL, the auth_redirect function was not redirecting to the Shared SSL URL.
118 * Bug Fix - If the home_url contained 'www' but the URL appeared without 'www', the URL would not be fixed.
119 * Standards - Updated redirect method to use https or http as a an argument rather than true or false to better comply with WordPress coding standards.
120 = 1.9 =
121 * Created Updates widget on settings screen to allow for dynamic updates from the plugin developers.
122 * Added support for PHP4.
123 * Converted all spaces to tabs in source.
124 * Force Shared SSL Admin option added to allow those using Shared SSL the ability to use their certificate for their admin dashboard.
125 * Bug fix - Force SSL checkbox will now appear on WordPress versions below 2.9.
126 * Bug fix - Password protected pages forced to SSL will now work properly.
127 * Bug fix - Plugin should no longer break feeds.
128 * Numerous other bug fixes that have since been forgotten due to the length of time this version has been in development.
129 = 1.8.5 =
130 * In version 1.8.5, when a page is forced to HTTPS, any links to that page will always be HTTPS, even when using the 'Disable Automatic HTTPS' option. Likewise, when the 'Force SSL Exclusively' option is enabled, all links to pages not forced to HTTPS will be changed to HTTP on HTTPS pages.
131 * Updated RegEx's for more complicated URL's.
132 * Bug fix - When in the admin panel, only link URL's are changed back to HTTP again.
133 * Added support for using Shared SSL together with the FORCE_SSL_ADMIN and FORCE_SSL_LOGIN options.
134 = 1.8.1 =
135 * Re-enabled the canonical redirect for WordPres sites not using Shared SSL.
136 = 1.8 =
137 * Fixed cross-browser CSS issue on plugin settings page.
138 * Corrected and updated plugin settings validation.
139 * Lengthened the fade out timer on messages from the plugin settings page from 2 to 5 seconds so that the more lengthy error messages could be read before the message faded.
140 * If viewing an admin page via SSL, and your Home URL is not set to HTTPS, links to the front-end of the website will be forced to HTTP. By default, WordPress changes these links to HTTPS.
141 * When using Shared SSL, any anchor that links to the regular HTTPS version of the domain will be changed to use the Shared SSL Host.
142 * Added embed and param tags to the list of tags that are fixed by WordPress HTTPS. This is to fix flash movies.
143 = 1.7.5 =
144 * Bug fix - When using 'Latest Posts' as the front page, the front page would redirect to HTTP when viewed over HTTPS even if the 'Force SSL Exclusively' option was disabled.
145 * Prevented the 'Disable Automatic HTTPS' option from parsing URL's in the admin panel.
146 * General code cleanup and such.
147 = 1.7 =
148 * Bug fix - External URL's were not being forced to HTTPS after the last update.
149 * Added the functionality to correct relative URL's when using Shared SSL.
150 * General code cleanup and such.
151 = 1.6.5 =
152 * Added support for Shared SSL.
153 = 1.6.3 =
154 * Changed the redirection check to use `template_redirect` hook rather than `get_header`.
155 = 1.6.2 =
156 * Tag links were not being set back to HTTP when the 'Disable Automatic HTTPS' option was enabled.
157 = 1.6.1 =
158 * Bug fix - front page redirection was causing issues when a static page was selected for the posts page.
159 = 1.6 =
160 * Added the ability to force the front page to HTTPS.
161 * Multiple enhancements to core functionality of plugin. Mostly just changing code to integrate more smoothely with WordPress.
162 * Enhancements have been made to the plugin's settings page.
163 = 1.5.2 =
164 * Fixed a bug that would prevent stylesheets from being fixed if the rel attribute came after the href attribute. Bug could have also caused errors with other tags.
165 = 1.5.1 =
166 * Added input elements with the type of 'image' to be filtered for insecure content.
167 = 1.5 =
168 * Added the ability to force SSL on certain pages.
169 * Also added the option to exclusively force SSL on certain pages. Pages not forced to HTTPS are forced to HTTP.
170 * Plugin now filters the `bloginfo` and `bloginfo_url` functions for HTTPS URL's when the 'Disable Automatic HTTPS' option is enabled in WordPress 3.0+.
171 = 1.0.1 =
172 * Bug fix.
173 = 1.0 =
174 * Major modifications to plugin structure, efficiency, and documentation.
175 * Added the option to disable WordPress 3.0+ from changing all of your page, category and post links to HTTPS.
176 = 0.5.1 =
177 * Bug fix.
178 = 0.5 =
179 * Due to increasing concerns about plugin performance, the option to bypass the HTTPS check on external elements has been added.
180 = 0.4 =
181 * Plugin functions converted to OOP class.
182 * The plugin will now attempt to set the allow_url_fopen option to true with `ini_set` function if possible.
183 = 0.3 =
184 * Added the option to change external elements to HTTPS if the external server allows the elements to be accessed via HTTPS.
185 = 0.2 =
186 * Changed the way in which HTTPS was detected to be more reliable.
187 = 0.1 =
188 * Initial Release.
190 == Upgrade Notice ==
191 = 1.7 =
192 1.6.5 created a bug in which external elements were no longer forced to HTTPS. Please update to fix this.
193 = 1.6.1 =
194 Version 1.6.1 fixes a bug with using a static page for the posts page.
195 = 1.0.1 =
196 Version 1.0.1 fixes a bug in 1.0 that made it to release. Apologies!
197 = 1.0 =
198 Version 1.0 gives you the ability to disable WordPress 3.0+ from changing all of your page, category and post links to HTTPS.
199 = 0.5.1 =
200 Fixes `PHP Warning: Invalid argument supplied for foreach()` error.
201 = 0.3 =
202 Version 0.3 gives you the option to change external elements to HTTPS if the external server allows the elements to be accessed via HTTPS.
203 = 0.2 =
e30d8fd @mvied Updated with 2.0.4 change log.
204 Version 0.1 did not correctly detect HTTPS on IIS and possibly other servers. Please update to version 0.2 to fix this issue.
Something went wrong with that request. Please try again.