| 开发者 | mianrashid |
|---|---|
| 更新时间 | 2026年8月19日 11:15 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
http:// version of your pages. And old http:// links are still sitting in your posts, your theme options and your page builder content, so the browser refuses to show the padlock.
This plugin fixes both, and shows you which one you actually have.
Send everyone to HTTPS
One click writes a 301 redirect so anyone arriving on http:// lands on https:// instead. If your site sits behind Cloudflare or another CDN, tick CDN / Proxy Mode to avoid a redirect loop.
Clear mixed content warnings
Images, scripts and stylesheets still loading over http:// are what break the padlock. The plugin rewrites them as the page is sent to the browser, so the fix applies everywhere at once. Nothing in your database is touched, and on a site that is not on HTTPS yet it stays switched off, so it is safe to install before your certificate is ready.
This part needs WordPress 6.9 or newer. On older versions use the Database Scanner below, which is the better fix anyway.
Clean up your database
The permanent fix. Scan every table for old http:// links, see exactly what would change, then apply it. Content from Elementor, Divi and WooCommerce is handled safely, which a plain search-and-replace cannot do.
What this plugin does not do
bluearctic-https-fixer folder to /wp-content/plugins/.Only if your certificate is not actually working. Load https://yoursite.com and check you get a padlock first. The Status tab warns you if it cannot find a valid certificate.
Tick CDN / Proxy Mode on the HTTPS Redirect tab. Sites behind a proxy can end up in a redirect loop without it, because the proxy handles the certificate and your server still sees plain HTTP.
Click "Remove Redirect Rules from .htaccess". Only this plugin's block is removed and the rest of your file is left alone. It also happens automatically when you deactivate the plugin.
No. It rewrites links in the page on its way to the browser. Deactivate the plugin and it is as though it was never installed.
The plugin shows you the exact block to paste in yourself, above the WordPress permalink rules. Nginx and IIS do not use .htaccess at all, so on those you add the rule to your server configuration instead. The plugin shows you that version too.
Scanning changes nothing at all. The fix step asks you to confirm first and works through rows in small batches. Take a database backup before you run it.
No. Those store their settings in a packed format that a plain search-and-replace corrupts, which is the usual reason a site breaks after a manual URL swap. The scanner unpacks it, changes the links, and repacks it correctly.
Not yet. Single site only in 1.0.
A few settings in your own database, plus the result of your last scan. Nothing is sent anywhere, ever. Everything is removed if you delete the plugin.