WP Force SSL

Description

This plugin helps you redirect HTTP traffic to HTTPS without the need of touching any code.

Want to contribute? Visit our GitLab repo.

Notes:

  • You need an SSL Certificate in order for this plugin to work.
  • You need to add https to the WordPress Address (URL) and Site Address (URL) parameters under General > Settings. (Required by WordPress itself)

Installation

You need to add https to the WordPress Address (URL) and Site Address (URL) parameters under General > Settings. (Required by WordPress itself)

  1. Add https to the WordPress Address (URL) and Site Address (URL) parameters under General > Settings. (Required by WordPress itself)
  2. Install as a regular WordPress plugin.
  3. Activate the plugin.
  4. Done.

Reviews

Everything I wanted from this

This did exactly what I needed. It was quick, easy and completely effective.

Note to some of the bad-review posters: this does not set up SSL for you. It also doesn’t fix errors or warnings. You have to do that yourself. All this will do is redirect people who deep link using non-SSL links to the SSL version of the same link on your site.

no luck

7 mixed content errors before installing. 7 mixed content errors after installing.

Super!

This is a great little tool that made all my problems vanish 🙂

I already had the SSL-certificate installed on the server and the wordpress-settings switched to https. Then I tried to redirect the non-https-articles and pages to https – to no avail. I tried several different entries for the .htaccess but that didn’t work at all (I still don’t know if it was because of some server-settings at 1und1).
Anyhow, in my research I stumbled upon the Force SSL-Plugin, installed it and WOW: everything now works just fine – even with the www (which I wanted to maintain).
I’m so happy! 🙂

Read all 43 reviews

Contributors & Developers

“WP Force SSL” is open source software. The following people have contributed to this plugin.

Contributors

Translate “WP Force SSL” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.4

  • Changed function naming to avoid conflicts reported by users.

1.3

  • 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.

1.2.1

  • Fixed an issue where some users were getting a error message for no valid header when activating the plugin.

1.2

  • 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.