v1.6.11
This commit is contained in:
parent
b81db2d302
commit
b5d03b7f81
1 changed files with 124 additions and 23 deletions
23
readme.txt
23
readme.txt
|
|
@ -4,7 +4,7 @@ Tags: security, two-factor authentication, login, otp
|
|||
Requires at least: 7.0
|
||||
Tested up to: 7.2
|
||||
Requires PHP: 8.3
|
||||
Stable tag: 1.6.10
|
||||
Stable tag: 1.6.11
|
||||
License: GPLv3 or later
|
||||
License URI: https://www.gnu.org/licenses/gpl-3.0.html
|
||||
|
||||
|
|
@ -59,6 +59,15 @@ Yes. Activate the plugin at the network level. Network administrators can set an
|
|||
|
||||
== 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 (Restrict Content Pro's "Hijack Login URL" and any plugin using the same `login_form_login` redirect pattern). Stage requests now carry a dedicated login action that such redirects cannot intercept, verified end to end on the reported replica: password at the membership page → verification screen → valid code → back on the membership page, logged in.
|
||||
* Users logging in from front-end forms now return to the page they logged in from after completing 2FA instead of landing in wp-admin.
|
||||
|
||||
= 1.6.10 =
|
||||
|
||||
_Release date: 2026-11-03_
|
||||
|
|
@ -92,18 +101,6 @@ _Release date: 2026-11-03_
|
|||
* PHPCompatibility: 8.3-8.6 — 0 issues
|
||||
* PHPUnit: 9.6.38 — 110 tests, 220 assertions
|
||||
|
||||
= 1.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.
|
||||
|
||||
**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 and the error message asks the user to sign in again.
|
||||
|
||||
= Previous versions =
|
||||
|
||||
For the full changelog see the [changelog](https://www.robotstxt.software/plugins/robotstxt-2fa/) page.
|
||||
|
|
|
|||
Loading…
Reference in a new issue