WP Force SSL

Omschrijving

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)

Installatie

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.

Beoordelingen

Wonderful!

It is as easy to set up as following the instructions. All links are cleaned-up and no headaches! Thank you!

Works

If it's not working on your site, make sure you follow the directions. At first I couldn't get it working, but you have to do exactly in following order: 1. Set your URL in WP - General to the version with "https://". Even if you already did this, just save it before activating plugin just to make sure. 2. Activate plugin. If you do it in reverse order, you might not get it working.

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.
Lees alle 47 beoordelingen

Bijdragers & ontwikkelaars

“WP Force SSL” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

Vertaal “WP Force SSL” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via 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.