PluginProbe ʕ •ᴥ•ʔ
WP Force SSL & HTTPS SSL Redirect / 1.70
WP Force SSL & HTTPS SSL Redirect v1.70
1.70 trunk 1.4 1.5 1.55 1.56 1.57 1.60 1.65 1.66 1.67 1.68 1.69
wp-force-ssl / readme.txt
wp-force-ssl Last commit date
css 2 days ago img 4 years ago inc 11 months ago js 2 days ago wf-flyout 4 years ago index.php 6 years ago license.txt 6 years ago readme.txt 2 days ago wp-force-ssl.php 2 days ago
readme.txt
152 lines
1 === WP Force SSL & HTTPS SSL Redirect ===
2 Contributors: WebFactory
3 Tags: ssl, force ssl, https, ssl certificate, mixed content
4 Requires at least: 4.6
5 Tested up to: 7.0
6 Requires PHP: 5.2
7 Stable Tag: 1.70
8 License: GPLv2 or later
9 License URI: http://www.gnu.org/licenses/gpl-2.0.html
10
11 Enable SSL & HTTPS redirect with 1 click! Add SSL certificate & WP Force SSL to redirect site from HTTP to HTTPS & fix SSL errors.
12
13 == Description ==
14
15 <a href="https://wpforcessl.com/?ref=wporg">WP Force SSL</a> helps you redirect insecure HTTP traffic to secure HTTPS and fix SSL errors **without touching any code**. Activate Force SSL and everything will be set and SSL enabled. The entire site will move to HTTPS using your SSL certificate. It works with any SSL certificate. It can be free SSL certificate from Let's Encrypt or a paid SSL certificate.
16
17 How to add SSL & enable SSL? Most hosting companies support the free SSL certificate from Let's Encrypt, so login to your hosting panel and add SSL certificate. You'll see a button labeled "Add SSL Certificate" or "Add Let's Encrypt Certificate" and after that it's 1 click to have the SSL enabled on your site with WP Force SSL. If that doesn't work get <a href="https://wpforcessl.com/">WP Force SSL PRO</a> and it'll generate free SSL certificate for your site. And will regenerate SSL certificate every 90 days.
18
19 Access WP Force SSL settings via the main Settings menu -> WP Force SSL.
20
21 = SSL Tests available in the plugin =
22 * is site on localhost?
23 * check SSL certificate
24 * check SSL certificate expiry date
25 * is latest version of Force SSL used?
26 * are known incompatible SSL plugins active?
27 * is WP address URL set for SSL?
28 * is WP home URL set for SSL?
29 * is SSL monitoring enabled (pro feature)
30 * is HTTPS redirection working?
31 * is file redirection working (pro feature)
32 * is HSTS enabled?
33 * check mixed-content issue (pro feature)
34 * is htaccess available & writable?
35 * is 404 redirection enabled (pro feature)
36
37 = Settings =
38 * redirect HTTP to HTTPS
39 * fix mixed-content (pro)
40 * enable HSTS
41 * force secure cookies (pro)
42 * cross-site scripting protection (pro)
43 * expect CT header
44 * X-Frame options
45 * show WP Force SSL menu in admin bar
46 * show WP Force SSL widget in admin dashboard
47
48 = SSL certificate testing tool =
49 WP Force SSL comes with an SSL certificate testing tool. It tests if the SSL certificate is valid, properly installed & up-to date.
50
51 = Need support? =
52 We're here for you! Things get frustrating when they don't work so make sure you <a href="https://wordpress.org/support/plugin/wp-force-ssl/">open a support topic</a> in the official Force SSL forum. We answer all questions within a few hours!
53
54 = External Assets =
55 A big thank you to <a href="https://sweetalert2.github.io/">SweetAlert2</a> authors which we use to make alerts nicer. And to <a href="https://depositphotos.com/248496280/stock-illustration-online-payment-protection-system-concept.html">DepositPhotos</a> for the lovely header image.
56
57
58 == Frequently Asked Questions ==
59
60 = Who is this plugin for? =
61 For anyone who has an SSL certificate installed on their site and wants to be sure all content is accessed (and redirected if needed) via a secure connection.
62
63 = Do I need an SSL certificate for this to work? =
64 Yes, you do need an SSL certificate. If you don't have one you can buy <a href="https://wpforcessl.com/">WP Force SSL PRO</a> which will generate an SSL certificate for free.
65
66 = After activating WP Force SSL, do I need to do anything else? =
67 No, nothing. After activating WP Force SSL, the main option "redirect SSL" will already be active. What you can do is use our tests to make sure everything related to SSL is working.
68
69 = How can I report security bugs? =
70 You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. [Report a security vulnerability.](https://patchstack.com/database/vdp/wp-force-ssl)
71
72 == Screenshots ==
73
74 1. Built-in tests verify your SSL configuration
75 2. SSL settings
76 3. SSL certificate tester
77
78 == Installation ==
79
80 1. Open Plugins - Add New in WP admin and search for "WP Force SSL"
81 2. Install and activate the plugin
82 3. Open plugin settings via Settings - WP Force SSL
83 4. Check provided tests and settings
84
85
86 == Changelog ==
87 = v1.70 =
88 - 2026/07/20
89 - minor update
90
91 = v1.69 =
92 - 2026/05/19
93 - minor update
94
95 = v1.68 =
96 - 2025/07/31
97 - minor code fixes
98
99 = v1.67 =
100 - 2024/06/07
101 - Security fixes
102
103 = v1.66 =
104 - 2024/03/26
105 - WordPress 6.5 and PHP 8.2 compatibility
106
107 = v1.65 =
108 - 2022/01/12
109 - added admin Dashboard widget
110
111 = v1.60 =
112 - 2021/12/28
113 - new GUI & features
114 - PRO version available
115
116 = v1.57 =
117 - 2021/01/30
118 - added flyout menu
119
120 = v1.56 =
121 - 2020/09/30
122 - minor bug fixes
123 - added promo for WP 301 Redirects PRO
124 - 602,200 downloads; 100,000 installations
125
126 = v1.55 =
127 - 2020/01/22
128 - minor bug fixes
129 - 384,400 downloads; 90,000 installations
130
131 = v1.5 =
132 - 2019/09/23
133 - complete rewrite of entire WP Force SSL plugin
134 - added support for HSTS
135 - 288,290 downloads; 80,000 installations
136
137 = v1.4 =
138 - Changed function naming to avoid conflicts reported by users.
139
140 = v1.3 =
141 - Dropping support for PHP 5.3: Only 15.9% of the people that use WordPress use PHP 5.3, it reached end of life and you should ask your host to upgrade.
142
143 = v1.2.1 =
144 - Fixed an issue where some users were getting a error message for no valid header when activating the plugin.
145
146 = v1.2 =
147 - Dropping support for PHP 5.2: Only 5.7% of the people that use WordPress use PHP 5.2, it's old, buggy, and insecure.
148
149 = v0.1 =
150 - 2015/01/15
151 - initial release
152