-
v1.6.11 Stable
released this
2026-11-04 18:43:35 +00:00 | 0 commits to main since this release1.6.11
Release date: 2026-11-04
Fixed
- The 2FA verification screen is no longer hijacked on membership sites that redirect the WordPress login away from wp-login.php (confirmed live on Restrict Content Pro 4.0.9 with "Hijack Login URL" enabled and the login at a custom account page such as /mi-cuenta/). RCP implements the hijack twice: through the login_url filter (already handled since 1.6.4) and — new finding — through a
login_form_loginredirect that bounces every default-action wp-login.php request to the membership page, dropping the 2FA query arguments. Stage requests now carry a dedicatedaction=robotstxt-2fa-verify(declared to WordPress via a registeredlogin_form_hook, preserved on submission through a hidden field), so they run core's login branch without firinglogin_form_login, out of reach of that redirect pattern in any plugin. Verified end to end on the reported replica: password at the membership page → verification screen renders → valid code → user lands back on the membership page, logged in. - Users logging in from front-end forms (membership/account pages) now return to the page they logged in from after completing 2FA instead of landing in wp-admin: when the request carries no core
redirect_to, the challenge falls back to the raw HTTP referer, validated to be same-host and not an admin or login URL (foreign and admin referers are ignored).
Compatibility
- WordPress: 7.0 - 7.2
- PHP: 8.3 - 8.6
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level max (10), no baseline — 0 errors
- PHPCompatibility: 8.3-8.6 — 0 issues
- PHPUnit: 9.6.38 — 125 tests, 236 assertions (PHP 8.6.0RC3 and 8.3.36)
- Live end-to-end on the reported site replica (WordPress 7.1.4 + Restrict Content Pro 4.0.9): full login → 2FA → return-to-page cycle, MariaDB 11.8.9
Downloads
- The 2FA verification screen is no longer hijacked on membership sites that redirect the WordPress login away from wp-login.php (confirmed live on Restrict Content Pro 4.0.9 with "Hijack Login URL" enabled and the login at a custom account page such as /mi-cuenta/). RCP implements the hijack twice: through the login_url filter (already handled since 1.6.4) and — new finding — through a
-
v1.6.10 Stable
released this
2026-11-04 14:39:03 +00:00 | 1 commits to main since this release1.6.10
Release date: 2026-11-03
Fixed
- The 2FA verification stage now stays on the login URL the visitor actually used. When wp-login.php executes through an alias or renamed slug (a
/loginrewrite, a "hidden login" setup that does not filtersite_url), the post-password redirect previously always targeted the literal/wp-login.php— on sites where that URL is blocked or renamed away at server level, users were stranded on a 403/404 page right after a correct password. The stage base URL now preserves the executing login surface (path only; host and scheme still come from the site's canonical URL; traversal sequences rejected), while logins submitted from custom pages callingwp_signon()keep landing on the real wp-login.php as before (the 1.6.4 Restrict Content Pro guarantee). Full root-cause analysis indocs/report-login-surface-urls.md.
Compatibility
- WordPress: 7.0 - 7.2
- PHP: 8.3 - 8.6
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level max (10), no baseline — 0 errors
- PHPCompatibility: 8.3-8.6 — 0 issues
- PHPUnit: 9.6.38 — 119 tests, 229 assertions (PHP 8.6.0RC3 and 8.3.36)
- Live surface probes: WordPress 7.2-beta4 (single site) and WordPress 7.0 (multisite) on PHP 8.6.0RC3, MariaDB 11.8.9
Downloads
- The 2FA verification stage now stays on the login URL the visitor actually used. When wp-login.php executes through an alias or renamed slug (a
-
v1.6.9 Stable
released this
2026-11-04 14:37:54 +00:00 | 2 commits to main since this release1.6.9
Release date: 2026-11-03
Changed
- Compatibility floors raised: minimum WordPress moved from 5.6 to 7.0 and minimum PHP from 8.0 to 8.3, matching the support policy (latest stable WordPress plus the two previous majors). The full-range compatibility review (WordPress 4.7-7.2 walked down with wp-compat; PHP 5.6-8.6 scanned with PHPCompatibility) confirmed the plugin uses no WordPress symbols newer than 6.0 and no PHP syntax newer than 8.0, so the real code floors are lower — the declared floors are the supported ones. WordPress 7.2 (beta 4, single-site) and WordPress 7.0 (multisite) were live-tested; PHP 8.6 (RC 3) was live-tested and PHP 8.3-8.6 scanned clean.
- The admin menu icon is now a brand SVG (shield with keyhole, base64 data URI) instead of
dashicons-shield, on both single-site and network admin menus. WordPress core natively renders base64 SVG menu icons (centered at 20px), so the icon works identically on WordPress 7.0, 7.1 and 7.2, stays crisp on high-density screens, and is future-proof against the admin-wide move from Dashicons to SVG icons tracked in WordPress core (PR #12270 / Trac ticket #65089). Dashicons continue to work everywhere else. - Composer tooling updated: wp-compat 3.0.1, PHPStan 2.3.5, wordpress-stubs 7.1.2, PHPUnit 9.6.38, maxmind-db/reader 1.14.0;
composer auditreports no known vulnerabilities.
Fixed
- PHP 8.6 deprecation removed: the REST controller declared a class constant named
namespace(case-insensitively), which PHP 8.6 deprecates and PHP 9 will reject as a fatal error. Renamed toREST_NAMESPACEwith no functional change (the constant was private). - Static-analysis hardening to pass PHPStan at the new maximum level (10) without a baseline:
$wpdb,$wp_filterand$postglobals are now properly typed; the uninstall routine deletes user meta through the$wpdb->delete()WordPress API instead of hand-built SQL; role names fromget_editable_roles()are validated before translation;AUTH_SALTandCOOKIEPATHare validated as strings before use in the trusted-device cookie; the trusted-device map discards corrupted non-string keys;get_users()results are instance-checked before use; a misplaced translators comment on an_n()call was fixed (WPCS error).
Compatibility
- WordPress: 7.0 - 7.2
- PHP: 8.3 - 8.6
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors, 1 accepted advisory warning (urlencode mirrors WordPress core's wp_login_url())
- PHPStan: 2.3.5 level max (10), no baseline — 0 errors
- PHPCompatibility: 9.3.5, testVersion 8.3-8.6 — 0 issues
- PHPUnit: 9.6.38 — 110 tests, 220 assertions (PHP 8.6.0RC3 and PHP 8.3.36)
- Live smoke tests: WordPress 7.2-beta4 (single site) and WordPress 7.0 (multisite) on PHP 8.6.0RC3, MariaDB 11.8.9
Downloads
-
v1.6.8 Stable
released this
2026-11-04 14:36:47 +00:00 | 3 commits to main since this release1.6.8
Release date: 2026-09-21
Added
- Administrator visibility when email delivery fails: failed verification-code deliveries record a marker and administrators see a persistent, self-clearing notice ("2FA: email delivery is failing…") in wp-admin and the network admin, since forced-email users cannot sign in while delivery is broken. The notice disappears automatically once a code is delivered successfully.
Fixed
- "We could not determine which account you are trying to access" during verification: the pending-stage token was stored in a transient, which external object caches (Redis/Memcached) can evict at any time, killing live verification sessions. Tokens now live in a persistent option map (capped, pruned, consumed on success, cleaned on uninstall) and the error message now says the session expired and asks the user to sign in again.
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 110 tests, 220 assertions
Downloads
-
v1.6.7 Stable
released this
2026-09-18 04:36:37 +00:00 | 4 commits to main since this release1.6.7
Release date: 2026-09-17
Fixed
- The forced-setup wizard felt like a broken redirect loop: the wizard redirect bounced users to the profile with no explanation (it now carries a flag that renders a clear "activate at least one verification method, then save" warning), and saving with an expired form nonce silently did nothing (it now raises a visible "form session expired" error so users know to try again).
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 98 tests, 197 assertions
Downloads
-
v1.6.6 Stable
released this
2026-09-17 10:59:06 +00:00 | 5 commits to main since this release1.6.6
Release date: 2026-09-17
Added
- Forced-enrollment warning on the profile 2FA section: when a user's role enforces 2FA but they have no verification method configured yet, the 2FA section of their profile (wp-admin and the frontend shortcode) opens with a warning notice asking them to activate at least one method. While a grace period is active, the notice appends the remaining days.
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 93 tests, 189 assertions
Downloads
-
v1.6.5 Stable
released this
2026-09-17 10:58:02 +00:00 | 6 commits to main since this release1.6.5
Release date: 2026-09-17
Fixed
- Fatal error on the login screen with newer WordPress versions: the
login_messagefilter can deliver null when no message is set (observed on WordPress 7.x with PHP 8.4, TypeError on a plain visit to wp-login.php). The message callback now acceptsstring|nulland coalesces null to an empty string. - Hardened all externally-fed filter callbacks against null payloads: the four
authenticatecallbacks now acceptstring|nullcredentials (custom REST/SSO endpoints are known to apply the filter with null), and thewp_redirectfilter callback coalesces a null location. Verified safe as-is: shortcode callback, Settings API sanitizer, activation hooks, and admin-hook parameters.
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 87 tests, 180 assertions
Downloads
- Fatal error on the login screen with newer WordPress versions: the
-
v1.6.4 Stable
released this
2026-09-11 10:30:35 +00:00 | 7 commits to main since this release1.6.4
Release date: 2026-09-11
Fixed
- Compatibility with Restrict Content Pro's "Hijack Login URL" option: RCP's
login_urlfilter made everywp_login_url()call return a membership page, so the 2FA verification redirect landed on a restricted page where the verification form cannot render, and the visitor was bounced to the registration page. Verification-stage URLs are now built from the canonicalwp-login.php, mirroring WordPress core's URL construction before the filterable output. The "Back to login" link keeps the site-configured login URL.
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 78 tests, 171 assertions
Downloads
- Compatibility with Restrict Content Pro's "Hijack Login URL" option: RCP's
-
v1.6.3 Stable
released this
2026-08-24 08:19:01 +00:00 | 8 commits to main since this release1.6.3
Release date: 2026-08-24
Changed
- Manager detection now uses the ecosystem presence constant (
ROBOTSTXT_MANAGER_NOTICED, defined by Manager 1.6.2+) with a fallback to the plugin-list scan for older Manager versions, so a stale plugin list can no longer produce false "Manager missing" notices.
Fixed
- Compatibility with the ALTCHA Spam Protection plugin: when "Protect login" was enabled, submitting the 2FA verification code failed with "[ALTCHA] Sorry, your request could not be processed.". The ALTCHA interceptor is now disabled while the verification screen is shown; the first login step keeps its ALTCHA check.
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 73 tests, 163 assertions
Downloads
- Manager detection now uses the ecosystem presence constant (
-
v1.6.2 Stable
released this
2026-08-17 15:56:31 +00:00 | 9 commits to main since this release1.6.2
Release date: 2026-08-17
Added
- Recommendation notice for the Manager (by ROBOTSTXT) plugin: when it is not installed and active, a dismissible notice appears on the Plugins screen and a permanent notice is shown on the plugin settings page, since updates are delivered through the Manager plugin.
Changed
- Updates are now handled by the Manager (by ROBOTSTXT) plugin. The bundled self-updater (robotstxt-updater.php and update.json) has been removed.
- Plugin and update URLs moved to robotstxt.software.
- Minimum WordPress version lowered from 6.4 to 5.6 after a full compatibility review (the code only requires WordPress 5.3+ functions, and WordPress 5.6 is the first release that runs on the required PHP 8.0).
Compatibility
- WordPress: 5.6 – 7.1
- PHP: 8.0 – 8.5
Tests
- PHP Coding Standards: PHP_CodeSniffer 3.13.6 / WPCS 3.4.1 — 0 errors
- PHPStan: level 9 — 0 errors
- PHPCompatibility: 8.0–8.5 — 0 issues
- PHPUnit: 9.6.36 — 59 tests, 148 assertions
Downloads