Gemini: WordPress 7.4 EOL (End of Life) Situation Question

• PHP’s official support cycle: PHP 7.4 officially reached its End-of-Life (EOL) for security support in November 2022. Running it in 2025 puts sites at significant, unpatched security risk.
• WordPress’s focus on broad compatibility: WordPress core historically moves cautiously to ensure a vast ecosystem of themes and plugins remains compatible with newer PHP versions. Delaying the mandatory notification gave developers and users more time to prepare for the jump to PHP 8+.
• Hosting provider changes: Many hosting providers have been removing PHP 7.4 as an option or automatically upgrading users, leading to an increasing push from the WordPress community to get the remaining stragglers off the outdated version.

Why Notifications Skipped PHP 8.0, 8.1, and 8.2

WordPress’s Site Health and official recommendations skipped directly to promoting a high PHP 8.x version, with PHP 8.4 being indicated as acceptable (or sometimes even recommending 8.3 or higher as the ideal version, depending on the current date), for the following reasons:

1. Phased and Delayed Core Compatibility

While PHP 8.0, 8.1, and 8.2 were released, WordPress core often took time to fully resolve all compatibility issues, which were sometimes labeled as “beta support” or “compatible with exceptions.”

• PHP 8.0 and 8.1: Full support was only retroactively declared in WordPress 6.3 (released August 2023) and later versions, after significant work was done to resolve known issues.
• PHP 8.2: Full support came even later, with WordPress 6.6 (released mid-2024).

Because full compatibility with 8.x was achieved gradually, and to provide maximum encouragement for users to move to the fastest and most secure supported version, WordPress tends to promote the newest stable version that has achieved “full support” status.

2. Targeting the Long-Term Stable Version

WordPress prefers to recommend versions that offer long-term stability, performance, and security.

• By the time WordPress fully ironed out compatibility for an earlier PHP 8.x version (like 8.0 or 8.1), a more performant and current version (like 8.3 or 8.4) was already available and rapidly approaching stability.
• The recommended version is often two to three versions ahead of the minimum supported version (which is PHP 7.2.24+ as a legacy environment minimum), encouraging users to jump straight to a version that will be supported for the longest time by the PHP development team, minimizing the need for another immediate update.

3. Avoiding Intermediate Upgrade Cycles

Each PHP version update, particularly the jump from PHP 7.4 to any PHP 8.x version, often introduces breaking changes that require plugins and themes to be updated.

• By encouraging a jump directly from the severely outdated 7.4 to a newer version like 8.4, WordPress minimizes the number of separate major PHP upgrades (e.g., 7.4 to 8.0, then 8.0 to 8.2, then 8.2 to 8.4) that users and developers would have to manage, focusing on one major, necessary security and performance leap.

In short, WordPress usually delays issuing strong warnings until a version is completely past its security EOL, and when it finally pushes for an update, it recommends the most stable, fully compatible, and current version to future-proof the site. The current recommended version is often PHP 8.3 or greater, with 8.4 being indicated as acceptable or next-in-line for full stability.