v1.6.11
This commit is contained in:
parent
b81db2d302
commit
b5d03b7f81
1 changed files with 124 additions and 23 deletions
|
|
@ -1,5 +1,27 @@
|
|||
== Changelog ==
|
||||
|
||||
= 1.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_login` redirect that bounces every default-action wp-login.php request to the membership page, dropping the 2FA query arguments. Stage requests now carry a dedicated `action=robotstxt-2fa-verify` (declared to WordPress via a registered `login_form_` hook, preserved on submission through a hidden field), so they run core's login branch without firing `login_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
|
||||
|
||||
= 1.6.10 =
|
||||
|
||||
_Release date: 2026-11-03_
|
||||
|
|
|
|||
Loading…
Reference in a new issue