v1.6.10
This commit is contained in:
parent
7379505d20
commit
b81db2d302
1 changed files with 100 additions and 15 deletions
18
readme.txt
18
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.9
|
||||
Stable tag: 1.6.10
|
||||
License: GPLv3 or later
|
||||
License URI: https://www.gnu.org/licenses/gpl-3.0.html
|
||||
|
||||
|
|
@ -59,6 +59,14 @@ Yes. Activate the plugin at the network level. Network administrators can set an
|
|||
|
||||
== Changelog ==
|
||||
|
||||
= 1.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 `/login` rewrite, a "hidden login" setup that does not filter `site_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. Logins submitted from custom pages keep landing on the real wp-login.php as before.
|
||||
|
||||
= 1.6.9 =
|
||||
|
||||
_Release date: 2026-11-03_
|
||||
|
|
@ -96,14 +104,6 @@ _Release date: 2026-09-21_
|
|||
|
||||
* "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.
|
||||
|
||||
= 1.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).
|
||||
|
||||
= Previous versions =
|
||||
|
||||
For the full changelog see the [changelog](https://www.robotstxt.software/plugins/robotstxt-2fa/) page.
|
||||
|
|
|
|||
Loading…
Reference in a new issue