• 1.6.10 b81db2d302

    v1.6.10 Stable

    javier released this 2026-11-04 14:39:03 +00:00 | 1 commits to main since this release

    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. 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 calling wp_signon() keep landing on the real wp-login.php as before (the 1.6.4 Restrict Content Pro guarantee). Full root-cause analysis in docs/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