WordPress 7.0 Beta 2 Is Here: How to Test It and What Changed Since Beta 1

WordPress 7.0 Beta 2 is available for testing, and it’s the kind of release that’s especially valuable for developers: mostly stabilization work (70+ fixes across Core and the Editor since Beta 1), plus one notable new feature that changes how external AI providers are managed inside wp-admin.

As with any beta, treat this as pre-release software. Don’t install it on production or mission-critical sites. Set up a dedicated test site or use a disposable environment so you can focus on validating upgrade paths, plugin/theme compatibility, and the specific areas that changed between betas.

Release timeline: mark April 9, 2026

WordPress 7.0 is currently scheduled for final release on April 9, 2026. If you like aligning your internal QA window with upstream milestones (especially if you ship client sites, plugins, or themes), it’s worth keeping an eye on the official schedule and upcoming 7.0-related Core posts as the release candidates approach.

If you want the broader feature overview for 7.0, the Beta 1 announcement is still the best place to catch up on the big changes; Beta 2 is primarily about hardening what’s already landed.

4 safe ways to test WordPress 7.0 Beta 2

You’ve got multiple routes to get Beta 2 running, depending on whether you prefer a GUI workflow, a ZIP install, command line automation, or a zero-setup browser sandbox.

1. WordPress Beta Tester plugin: Install and activate the WordPress Beta Tester plugin on an existing WordPress install. Select the “Bleeding edge” channel and “Beta/RC Only” stream.
2. Direct download (ZIP): Download WordPress 7.0 Beta 2 (zip) and install it on a WordPress website (in a test environment).
3. WP-CLI: Update a test install via WP-CLI using: wp core update --version=7.0-beta2
4. WordPress Playground: Use this ready-to-run WordPress Playground instance to test directly in your browser-no setup required.

wp core update --version=7.0-beta2

wp core update --version=7.0-beta2

What to test (and where to report issues)

The two highest-value testing tracks are (1) the upgrade process and (2) real-world feature usage. Start by running your usual update workflow, then move on to exercising editing flows, admin screens, and any plugin/theme code that touches Editor or Core APIs.

A dedicated guide is available here: Help test WordPress 7.0. It walks through the specific features and behaviors worth validating during the 7.0 cycle.

When you hit a problem, you have a few well-established paths:

• Report issues in the Alpha/Beta support forum.
• File a ticket in WordPress Trac if you’re comfortable writing a reproducible bug report.
• Cross-check against the current list of known bugs to avoid duplicates.
• Follow ongoing efforts via the Make WordPress Test site.
• Coordinate with other testers in the #core-test channel on Making WordPress Slack.

Beta 2 highlights: 70+ fixes, plus a new Connectors UI for AI providers

WordPress 7.0 Beta 2 includes more than 70 updates and fixes across the Editor and Core since Beta 1. That’s consistent with how beta cycles typically operate: the focus shifts from shipping new capabilities to tightening behavior, squashing regressions, and improving compatibility.

But Beta 2 does introduce one new user-facing feature: a more intuitive way to manage external AI provider connections via a new Connectors dashboard screen.

New: Settings → Connectors (centralized external AI connection management)

In WordPress 7.0 Beta 2, external AI connections can be managed in a single, centralized place in wp-admin: Settings → Connectors. The idea is straightforward: instead of scattering AI provider configuration across plugin-specific screens, users get a dedicated dashboard page where they can add, delete, and update external connections.

Under the hood, the new Connectors UI is designed to be extensible. It uses a route-based architecture, meaning plugins and themes can hook into the page and expand what it can do without resorting to fragile UI hacks. The page builds on existing PHP-based script and menu infrastructure, then layers in route components powered by @wordpress/components and @wordpress/admin-ui.

For developers, the important bit is the integration surface: a new connections-wp-admin-init hook plus registration APIs that let plugins integrate cleanly. That combination aims to make external connection management easier for site owners while giving developers a predictable, official way to plug into the experience.

Changelog deep dives: commits and closed tickets since Beta 1

If you prefer scanning raw engineering output-especially helpful when you’re assessing potential impact on custom blocks, Editor tooling, or admin customizations-these two links summarize what landed between Beta 1 and Beta 2:

• GitHub commits for 7.0 since February 20, 2026
• Closed Trac tickets for 7.0 since February 20, 2026

A Beta 2 haiku

New, and fresh as dew Crafted and refined for you: Beta 2 breaks through.

WordPress 7.0 Beta 2 release haiku

Quick recap

• WordPress 7.0 Beta 2 is ready for testing (avoid production environments).
• You can test via the Beta Tester plugin, ZIP download, WP-CLI, or WordPress Playground.
• The final release is currently scheduled for April 9, 2026.
• Beta 2 includes 70+ fixes across Core and the Editor since Beta 1.
• New feature: a Connectors UI at Settings → Connectors for centralized external AI connection management, built to be extensible via a route-based architecture, @wordpress/components, @wordpress/admin-ui, and the new connections-wp-admin-init hook plus registration APIs.