Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3648114,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3648114,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3648114,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3648114,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3648114,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3648114,"resolution":"1","location":"assets","locale":"","width":806,"height":652},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3648114,"resolution":"2","location":"assets","locale":"","width":806,"height":696},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3648114,"resolution":"3","location":"assets","locale":"","width":806,"height":617},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3648114,"resolution":"4","location":"assets","locale":"","width":806,"height":532}},"screenshots":{"1":"Status tab \u2014 shows SSL certificate, redirect, fixer, and WordPress URL health at a glance.","2":"HTTPS Redirect tab \u2014 enable the 301 redirect with optional CDN\/proxy mode and a live .htaccess preview.","3":"Mixed Content Fixer tab \u2014 configure the front-end URL rewriter with path exclusions.","4":"Database Scanner tab \u2014 scan all tables for http:\/\/ URLs, preview results, and fix with one click."}},"plugin_section":[],"plugin_tags":[1908,24593,727,600,1536],"plugin_category":[54],"plugin_contributors":[275771],"plugin_business_model":[],"class_list":["post-342649","plugin","type-plugin","status-publish","hentry","plugin_tags-https","plugin_tags-mixed-content","plugin_tags-redirect","plugin_tags-security","plugin_tags-ssl","plugin_category-security-and-spam-protection","plugin_contributors-mianrashid","plugin_committers-mianrashid"],"banners":{"banner":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/banner-772x250.png?rev=3648114","banner_2x":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/banner-1544x500.png?rev=3648114","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/icon.svg?rev=3648114","icon":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/icon.svg?rev=3648114","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/screenshot-1.png?rev=3648114","caption":"Status tab \u2014 shows SSL certificate, redirect, fixer, and WordPress URL health at a glance."},{"src":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/screenshot-2.png?rev=3648114","caption":"HTTPS Redirect tab \u2014 enable the 301 redirect with optional CDN\/proxy mode and a live .htaccess preview."},{"src":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/screenshot-3.png?rev=3648114","caption":"Mixed Content Fixer tab \u2014 configure the front-end URL rewriter with path exclusions."},{"src":"https:\/\/ps.w.org\/bluearctic-https-fixer\/assets\/screenshot-4.png?rev=3648114","caption":"Database Scanner tab \u2014 scan all tables for http:\/\/ URLs, preview results, and fix with one click."}],"raw_content":"\n
Bluearctic HTTPS Fixer does three things:<\/p>\n\n
1. HTTPS Redirect<\/strong>\nWrites a single, clean 301 redirect rule to your 2. Mixed Content Fixer (on by default, requires WordPress 6.9+)<\/strong>\nRewrites The rewrite runs on the template enhancement output buffer that WordPress manages itself, added in WordPress 6.9. The plugin never opens an output buffer of its own. On WordPress 6.8 and earlier this feature stays switched off and the Database Scanner below is the way to clear 3. Database Scanner<\/strong>\nScans your database for What Bluearctic HTTPS Fixer does not do:<\/strong>\n- No firewall\n- No vulnerability scanner\n- No login protection or 2FA\n- No upsells or upgrade prompts\n- No external API calls or phone-home\n- No automatic database changes<\/p>\n\n Enable \"CDN \/ Proxy Mode\" in the HTTPS Redirect tab. This adds an Yes. It rewrites your own domain's WordPress 6.9 introduced a template output buffer that plugins can filter, so a plugin no longer has to open a PHP output buffer of its own to modify a page. Bluearctic HTTPS Fixer uses only that buffer. That keeps the plugin out of the shared output buffer stack entirely, which is the safest way to do this and avoids conflicts with caching and optimisation plugins. On older WordPress the fixer is simply unavailable \u2014 everything else in the plugin works normally.<\/p>\n\n On WordPress 6.9+ the fixer handles these transparently at runtime. For a permanent fix on any version, use the Database Scanner<\/strong> tab \u2014 it scans every table, shows you exactly what will change with a full preview, and lets you apply the fix in one click. Serialized data (Elementor, WooCommerce, Divi) is handled correctly. Nothing is changed until you review and confirm.<\/p>\n\n\n Yes. Enable \"CDN \/ Proxy Mode\" in the HTTPS Redirect tab. This adds the X-Forwarded-Proto header check that Cloudflare and most other proxies use.<\/p><\/dd>\n Only if your SSL certificate is not installed. The Status tab shows a warning if no certificate is detected. Always confirm your certificate is active at Click \"Remove Redirect Rules from .htaccess\" in the HTTPS Redirect tab. Only the Bluearctic HTTPS Fixer block is removed; everything else in your .htaccess is untouched. The rules are also removed automatically when you deactivate or delete the plugin.<\/p><\/dd>\n No. It rewrites URLs in the page HTML on the fly, inside the output buffer WordPress manages. Your database is unchanged.<\/p><\/dd>\n The plugin will show you the exact rule block to copy. Paste it into your Single-site is fully supported in v1.0. Multisite support is planned for a future release.<\/p><\/dd>\n Yes. Both plugins store data as PHP serialized strings, which break if you do a naive search-and-replace (the byte-length annotations become wrong and WordPress cannot read the data). Bluearctic HTTPS Fixer unserializes the value, replaces URLs recursively, and re-serializes \u2014 keeping all annotations correct. Nested serialization (Elementor stores serialized strings inside serialized arrays) is handled as well.<\/p><\/dd>\n The scan is completely read-only \u2014 it changes nothing. The fix step updates rows in batches of 50, with a confirmation modal before anything is written. We strongly recommend a database backup before running the fix, and the plugin reminds you of this before you proceed.<\/p><\/dd>\n The HTTPS redirect rule is removed from Bluearctic HTTPS Fixer stores four options in .htaccess<\/code> file using WordPress's own insert_with_markers()<\/code> function \u2014 the same method WordPress uses for its own permalink rules. It is non-destructive, clearly marked, and trivially removable. Full support for sites behind Cloudflare, CDNs, and load balancers (X-Forwarded-Proto).<\/p>\n\nhttp:\/\/<\/code> to https:\/\/<\/code> in your front-end page output before it reaches the browser. This is completely non-destructive \u2014 nothing in your database is touched. It works the instant you activate the plugin on an HTTPS site, with zero configuration required. On a site still served over plain HTTP it stays dormant, so activating the plugin before your certificate is ready is completely safe. Only your own domain's URLs are rewritten; external URLs are never touched.<\/p>\n\nhttp:\/\/<\/code> URLs \u2014 it is the permanent fix in any case.<\/p>\n\nhttp:\/\/<\/code> URLs belonging to your site and lets you replace them with https:\/\/<\/code> in a controlled, step-by-step process. Every table is scanned read-only first \u2014 nothing is changed until you review the results and click Fix. Correctly handles serialized data used by Elementor, Divi, WooCommerce, and other page builders so byte-length annotations stay accurate. Covers posts, post meta, options, comments, term meta, and user meta.<\/p>\n\nCloudflare \/ CDN \/ Load Balancer support<\/h4>\n\n
X-Forwarded-Proto<\/code> check to the redirect rule, which prevents infinite redirect loops when SSL is terminated at the proxy level rather than your own server.<\/p>\n\nThe mixed content fixer is on by default \u2014 is that safe?<\/h4>\n\n
http:\/\/<\/code> URLs in the HTML before it is sent to the browser, using the output buffer WordPress 6.9 opens and closes around your template. Nothing is written to the database or the filesystem. It only runs once your site is actually serving HTTPS \u2014 on a plain-HTTP site it stays dormant, so it can never break a site that has no certificate yet. Deactivate the plugin and it is as if it was never there.<\/p>\n\nWhy does the fixer need WordPress 6.9?<\/h4>\n\n
What about database URLs still set to http:\/\/?<\/h4>\n\n
\n
bluearctic-https-fixer<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install directly from the WordPress plugin directory.<\/li>\n\n
Does Bluearctic HTTPS Fixer work with Cloudflare?<\/h3><\/dt>\n
Will enabling the redirect break my site?<\/h3><\/dt>\n
https:\/\/yoursite.com<\/code> before enabling the redirect.<\/p><\/dd>\nHow do I undo the .htaccess changes?<\/h3><\/dt>\n
Does the mixed content fixer change my database?<\/h3><\/dt>\n
My .htaccess is not writable. What do I do?<\/h3><\/dt>\n
.htaccess<\/code> file manually, before the WordPress permalink block. Note that .htaccess is specific to Apache and LiteSpeed servers \u2014 if you are running Nginx or IIS, you will need to add the redirect rule in your server configuration instead.<\/p><\/dd>\nIs this plugin compatible with multisite?<\/h3><\/dt>\n
Does the Database Scanner handle WooCommerce and Elementor data?<\/h3><\/dt>\n
Is the Database Scanner safe to run on a live site?<\/h3><\/dt>\n
What does Bluearctic HTTPS Fixer do when deactivated?<\/h3><\/dt>\n
.htaccess<\/code> automatically when you deactivate the plugin. Your settings are preserved so they are restored if you reactivate. WordPress Site URL and Home URL settings are not touched on deactivation \u2014 those are WordPress core settings and reverting them to HTTP could break a live HTTPS site.<\/p><\/dd>\nWhat data does this plugin store?<\/h3><\/dt>\n
wp_options<\/code>: bahf_redirect_enabled<\/code>, bahf_proxy_mode<\/code>, bahf_fixer_enabled<\/code>, and bahf_fixer_exclusions<\/code>. It also saves the last scan result (bahf_last_scan_time<\/code>, bahf_last_scan_count<\/code>) and a short-lived fix log as a transient. No data is sent to external servers. Everything is removed when the plugin is deleted.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n
insert_with_markers()<\/code>.<\/li>\nhttp:\/\/<\/code> URLs, handles serialized data (Elementor, WooCommerce, Divi), shows a preview, and fixes with explicit user confirmation in batches of 50 rows.<\/li>\n