Last checked and updated on 10 Jun 2026
What Is New in WordPress 5.2
WordPress 5.2, "Jaco," is a significant release focused on proactive site protection and developer tooling. It introduces critical features for handling fatal errors and modernizes the coding experience.
| Category | Key Changes |
|---|---|
| New Features | Site Health, PHP Error Protection, New Admin Email Verification |
| Developer Tools | WP_DEBUG_DISPLAY constant, Plugin Compatibility Checks, Date/Time Component Fixes |
| Accessibility | Improved Admin Accessibility |
| Block Editor | Accessibility and UI Improvements |
How does WordPress 5.2 protect my site from crashes?
It introduces PHP Error Protection, a major feature that defends your site from white screens of death caused by fatal errors. This system detects failures in plugins or themes and puts the site into recovery mode.
In recovery mode, an admin user is presented with an email-based verification screen to log in and fix the problem. This is a game-changer because it prevents a single bad plugin update from taking an entire site offline, a common headache for developers managing client sites.
What new tools are available for site maintenance?
WordPress 5.2 adds a pair of Site Health tools to give developers a clearer picture of their site's configuration. The Site Health Status page checks for common configuration issues and highlights recommendations.
The Site Health Info page provides a detailed overview of the server environment, PHP configuration, and installed plugins and themes. This is incredibly useful for debugging, as you can quickly copy this info to share with support teams instead of manually gathering server details.
What developer-focused updates should I know about?
A new WP_DEBUG_DISPLAY constant was introduced for more granular control over debug output. You can now set this to false to prevent errors from being printed on the screen, while still logging them to a file via WP_DEBUG_LOG.
The release also includes important fixes for the date and time components, making them more reliable. For plugin authors, there are new checks to warn users if a plugin requires a PHP or WordPress version that is too old, helping to prevent compatibility issues before they happen.
Were there any changes to the admin area?
Yes, the update includes a new process for verifying a change to the site administrator email address. This adds a security layer to prevent unauthorized changes to this critical account.
Accessibility in the WordPress admin received continued attention with various improvements, making the platform more usable for everyone. The Block Editor (Gutenberg) also saw its own set of accessibility and user interface refinements in this release.
FAQ
How does the new PHP Error Protection actually work?
When a fatal error occurs, WordPress catches it and enters "recovery mode." Instead of a white screen, an admin user will see a message prompting them to enter their email to receive a link. Clicking the link verifies their capability to fix the issue and grants access to the admin area to deactivate the problematic plugin or theme.
Where do I find the new Site Health tools?
Navigate to Tools > Site Health in your WordPress admin dashboard. The "Status" tab shows recommendations, while the "Info" tab provides a full, copy-pasteable report of your server's PHP version, WordPress configuration, and active extensions.
What's the practical use of the WP_DEBUG_DISPLAY constant?
Before 5.2, WP_DEBUG true would often print errors directly to the screen, which could break page layout or expose sensitive info on a live site. Now, you can set WP_DEBUG_DISPLAY to false to suppress on-screen errors while still logging them to wp-content/debug.log, making debugging on staging sites much cleaner.
Does the Plugin Compatibility Check block outdated plugins?
It doesn't block them, but it adds a new warning. If a plugin header specifies it requires a WordPress version older than 4.7 or a PHP version older than 5.6, a notice will appear on the Plugins screen alerting the user that the plugin is outdated and may not be compatible.
I changed my admin email and got a verification link. Is this new?
Yes, this is a new security feature in 5.2. Any attempt to change the administrator email address now triggers an email confirmation to the old address. The change is not finalized until the link in that email is clicked, preventing unauthorized changes through a compromised account.