Background: Dropping support for PHP 7.2 and 7.3
Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0, currently scheduled for release in April 2026. The minimum recommended version of PHP will remain at 8.3, but the new minimum supported version of PHP will be 7.4.0.
This further emphasizes the need to modernize our Playground blueprint — using an EOL PHP version (7.4) while WordPress itself is moving to require 7.4+ as minimum creates confusion for users testing the plugin.
Ref: https://make.wordpress.org/core/2026/01/09/dropping-support-for-php-7-2-and-7-3/
Problem
The current Playground blueprint in .wordpress-org/blueprints/blueprint.json has several issues that make it suboptimal for demonstrating the Two-Factor plugin:
-
Outdated PHP version — The blueprint uses PHP 7.4. While WordPress 7.0 will make PHP 7.4 the new minimum supported version, the minimum recommended version remains PHP 8.3. PHP 7.4 reached end-of-life on November 28, 2022 and no longer receives security updates. The Playground demo should use the recommended PHP version (8.2 or higher) to set a good example for users testing the plugin.
-
Verbose plugin syntax — The plugins array uses a verbose FileReference object when the schema supports simple string slugs for WordPress.org plugins, making the blueprint harder to read.
-
Unclear plugin activation — The plugins shorthand installs the plugin but doesn't explicitly guarantee activation. Users landing on the profile page may not see Two-Factor options if the plugin isn't activated.
-
Login step not using shorthand — The login configuration is embedded in the steps array instead of using the cleaner top-level login shorthand property.
Proposed Solution
Update the blueprint to:
- Use PHP 8.2 (modern, actively supported)
- Simplify
plugins syntax to "two-factor" string
- Add explicit
activatePlugin step to ensure plugin is active
- Use top-level
login: true shorthand
References
Background: Dropping support for PHP 7.2 and 7.3
Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0, currently scheduled for release in April 2026. The minimum recommended version of PHP will remain at 8.3, but the new minimum supported version of PHP will be 7.4.0.
This further emphasizes the need to modernize our Playground blueprint — using an EOL PHP version (7.4) while WordPress itself is moving to require 7.4+ as minimum creates confusion for users testing the plugin.
Ref: https://make.wordpress.org/core/2026/01/09/dropping-support-for-php-7-2-and-7-3/
Problem
The current Playground blueprint in
.wordpress-org/blueprints/blueprint.jsonhas several issues that make it suboptimal for demonstrating the Two-Factor plugin:Outdated PHP version — The blueprint uses PHP 7.4. While WordPress 7.0 will make PHP 7.4 the new minimum supported version, the minimum recommended version remains PHP 8.3. PHP 7.4 reached end-of-life on November 28, 2022 and no longer receives security updates. The Playground demo should use the recommended PHP version (8.2 or higher) to set a good example for users testing the plugin.
Verbose plugin syntax — The
pluginsarray uses a verboseFileReferenceobject when the schema supports simple string slugs for WordPress.org plugins, making the blueprint harder to read.Unclear plugin activation — The
pluginsshorthand installs the plugin but doesn't explicitly guarantee activation. Users landing on the profile page may not see Two-Factor options if the plugin isn't activated.Login step not using shorthand — The login configuration is embedded in the
stepsarray instead of using the cleaner top-levelloginshorthand property.Proposed Solution
Update the blueprint to:
pluginssyntax to"two-factor"stringactivatePluginstep to ensure plugin is activelogin: trueshorthandReferences