Šī spraudnis nav atjaunināts vairāk kā divus gadus. Varbūt, tas vairs netiek uzturēts, nesaņemt atbalstu un tam var būt saderības problēmas ar jaunākām WordPress versijām.

HTTPS force

Apraksts

A fix for mixed content on secure sites, as all links and references to local content are converted to HTTPS.
Can redirect all requests for HTTP to HTTPS.

Also works for the administration area!

Main Features

  • Makes every Plugin compatible with https
  • Fixes Google Fonts issues
  • Can redirect to secure (https) site

Example

Without Plugin:
“http://domain.com/script1.js”
“https://domain.com/script2.js”

With Plugin:
“https://domain.com/script1.js”
“https://domain.com/script2.js”

Note

The Plugin does not force https on external links. This might be added later, but this plugin cannot determine if the remote site can handle HTTPS requests or not..

Other Cache Plugin:
Please purge/clear cache for the changes to take effect!

More

Feel free to visit our Website

Uzstādīšana

  1. Upload https-force folder to your /wp-content/plugins/ directory.
  2. Activate the plugin from Admin > Plugins menu
  3. Go to Admin > Settings > General
  4. Enable replacing insecure elements and/or redirect to secure site

Atsauksmes

Par šo spraudni nav atsauksmju.

Autori un izstrādātāji

“HTTPS force” ir atvērtā pirmkoda programmatūra. Šo spraudni ir veidojuši šādi cilvēki.

Līdzdalībnieki

Tulkot “HTTPS force” savā valodā.

Vai jūs interesē attīstība?

Pārlūkojiet kodu, apmeklējiet SVN krātuvi vai abonējiet attīstības žurnālu, ko izveidojis RSS.

Izmaiņu žurnāls

1.1.0 (18/01/19)

  • Added settings to WordPress general tab, to enable replacing insecure elements and/or redirecting
  • In doing so, minimum required version is now WP 2.7.0
  • Important for those updating: Default value for both settings is DISABLED. You need to enable in Admin > Settings > General

1.0.3 (17/01/19)

  • Tested and confirmed compatible with WP 5.0.3
  • Added check if requested page is an administrative interface page for certain pattern

1.0.2 (17/07/18)

  • Tested and confirmed compatible with WP 4.9.7

1.0.1 (16/01/18)

  • Tested and confirmed compatible with WP 4.9.1

1.0.0 (17/07/17)

  • Initial release