v1.6.2
This commit is contained in:
parent
1f7343cd9d
commit
3e4433cd13
1 changed files with 1720 additions and 441 deletions
40
readme.txt
40
readme.txt
|
|
@ -1,10 +1,10 @@
|
|||
=== 2FA (by ROBOTSTXT) ===
|
||||
Contributors: robotstxt
|
||||
Contributors: robotstxt, javiercasares
|
||||
Tags: security, two-factor authentication, login, otp
|
||||
Requires at least: 6.4
|
||||
Requires at least: 5.6
|
||||
Tested up to: 7.0
|
||||
Requires PHP: 8.0
|
||||
Stable tag: 1.6.1
|
||||
Stable tag: 1.6.2
|
||||
License: GPLv3 or later
|
||||
License URI: https://www.gnu.org/licenses/gpl-3.0.html
|
||||
|
||||
|
|
@ -53,12 +53,26 @@ Yes. Activate the plugin at the network level. Network administrators can set an
|
|||
|
||||
== Compatibility ==
|
||||
|
||||
* WordPress: 6.4 – 7.0
|
||||
* WordPress: 5.6 – 7.0
|
||||
* PHP: 8.0 – 8.5
|
||||
* MariaDB: 11.4 or newer
|
||||
|
||||
== Changelog ==
|
||||
|
||||
= 1.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).
|
||||
|
||||
= 1.6.1 =
|
||||
|
||||
_Release date: 2026-08-14_
|
||||
|
|
@ -82,25 +96,9 @@ _Release date: 2026-08-07_
|
|||
|
||||
* `wp 2fa list` now shows separate **Enabled**, **Methods** (configured), and **Required** (role-enforced) columns, plus a new `--required` filter to list only users whose role enforces 2FA.
|
||||
|
||||
= 1.5.3 =
|
||||
|
||||
_Release date: 2026-08-07_
|
||||
|
||||
**Added**
|
||||
|
||||
* Per-user preferred sign-in method — a new "Preferred method" dropdown on the user profile (visible when two or more methods are enabled) lets each user choose which verification method is requested first at the login screen. Users can still switch methods on the login screen via the existing alternate-method links.
|
||||
|
||||
**Changed**
|
||||
|
||||
* Role enforcement is now a floor, not a ceiling. When a role requires specific methods, those methods are still forced on the user's profile (enforced setup), but at login users may authenticate with any method they have configured — not only the role-required ones. Previously, users who configured extra methods (e.g. an authenticator app) only saw the role-required method at login.
|
||||
|
||||
**Fixed**
|
||||
|
||||
* Security: the "Require 2FA to create Application Passwords" check could be bypassed via the `/wp/v2/users/me/application-passwords` REST route. The route matcher now accepts the `me` alias.
|
||||
|
||||
= Previous versions =
|
||||
|
||||
For the full changelog see the [changelog.txt](https://git.robotstxt.es/ROBOTSTXT/robotstxt-2fa/raw/branch/main/changelog.txt) file.
|
||||
For the full changelog see the [changelog](https://www.robotstxt.software/plugins/robotstxt-2fa/) page.
|
||||
|
||||
== Compliance ==
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue