WordPress 7.0 Release Candidate 2 Is Ready for Testing: What to Check Before April 9

Detail	Value
Difficulty	Beginner
Estimated time	5 minutes to a full afternoon, depending on scope
Prerequisites	None required — a staging/test WordPress install recommended
Planned final release	April 9, 2026

WordPress 7.0 RC2 is the last pre-release checkpoint before the stable version ships. This post covers what an RC actually means, exactly what to test in RC2, what changed since RC1, and how to report anything you find broken — all before the April 9, 2026 cutoff.

What Is a WordPress Release Candidate?

A Release Candidate (RC) is the final phase of the WordPress release cycle before the stable version ships. By this point, all planned features are locked in and major bugs are resolved — the remaining work is stability verification and edge-case testing.

RC2 specifically means issues were found in RC1, fixed, and now need a second round of broad testing before the team is confident enough to tag the release as final. It's the last call before the door closes.

Release Stage	Purpose	Production Safe?
Beta	Feature-complete, early bug hunting	❌ No
Release Candidate 1	Near-final, broad compatibility testing	❌ No
Release Candidate 2	Targeted fixes from RC1, final stability check	❌ No
Final Release	Stable, recommended for all sites	✅ Yes

Step 1 — Set Up Your Test Environment

Before testing RC2, you need a safe sandbox. Pick one of these four options based on your setup and comfort level:

1. WordPress Beta Tester Plugin — Install and activate the WordPress Beta Tester plugin on an existing test site. In its settings, choose the Bleeding Edge channel and the Beta/RC Only stream. Easiest if you already have a test site running.
2. Direct Download — Download the RC2 zip file from WordPress.org and install it manually on a staging server for full control.
3. WP-CLI — If you manage WordPress from the command line, run:

   wp core update --version=7.0-rc2

   Fastest option for developers already SSH'd into a test server.
4. WordPress Playground — No server needed. Open the WordPress Playground instance directly in your browser for quick feature testing with zero setup.

Step 2 — Know What to Test in WordPress 7.0

RC2 testing is focused on stability, not discovery. Still, WordPress 7.0 ships with significant new capabilities that benefit from real-world testing across diverse environments. Two priority areas were flagged by the core team:

Real-Time Collaboration

WordPress 7.0 introduces real-time co-editing in the block editor. Multiple users can work on the same post simultaneously, with changes appearing live for all collaborators. Testing this requires two browser sessions or two user accounts — it's the feature most likely to surface environment-specific issues.

Pattern Editing & Content-Only Interactivity

Synced block patterns now support content-only editing mode, letting editors update text and images inside a pattern without breaking its underlying structure. Test by creating synced patterns, entering content-only mode, making edits, and verifying the pattern structure stays intact across every page where it's used.

Step 3 — Review What Changed Since RC1

RC2 is a targeted update, not a feature addition. Every change since RC1 (tagged March 24, 2026) is a bug fix or stability improvement. Two ways to dig into specifics:

1. GitHub Commits — Browse the Gutenberg commits between March 24–26, 2026 to see which block editor changes landed in RC2.
2. Trac Tickets — Review the closed Trac tickets from the same window for core PHP/JS fixes, filtered by component.

If you reported an issue against RC1, this is the right moment to check whether it appears in the closed tickets list — and re-test if it does.

Step 4 — Report Issues the Right Way

Found something broken? How you report it matters. Pick based on your comfort level:

1. Support Forums (Alpha/Beta area) — Post to the Alpha/Beta forum if you found an issue but aren't sure how to write a formal bug report. Describe reproduction steps, your environment (PHP version, active plugins, theme), and expected vs. actual behavior.
2. WordPress Trac — File directly on Trac if you can write a reproducible report. Check the known bugs list first to avoid duplicates.
3. Core Test Slack — Join the #core-test channel on Making WordPress Slack for real-time discussion with the testing team.

Bonus: Update Your Plugin or Theme Compatibility

If you maintain a WordPress plugin or theme, RC2 is your last realistic window to finish compatibility testing before the April 9 release date. Once 7.0 ships, users start updating, and any incompatibility becomes a user-facing problem.

Most important action: update the Tested up to field in your plugin's readme.txt to 7.0 once you've confirmed compatibility — this tells users on WordPress.org your plugin is ready. Found a compatibility issue instead? Post it to the Alpha/Beta support forum.

Troubleshooting Common RC2 Issues

Symptom	Likely Cause	Fix
White screen after update	Plugin conflict or PHP memory limit	Deactivate all plugins, re-enable one by one
Block editor fails to load	JS conflict from a plugin	Check browser console for errors, isolate plugin
Real-time collab not working	WebSocket blocked by server/firewall	Test on WordPress Playground to confirm it's environment-specific
Synced patterns reverting	Caching plugin serving stale content	Disable caching plugin during testing
Upgrade fails via Beta Tester plugin	File permission issue on server	Use the direct download method instead

RC2 Testing Checklist

• ✅ Installed RC2 on a test/staging site (never on production)
• ✅ Tested real-time collaboration with two user accounts
• ✅ Tested pattern editing in content-only mode
• ✅ Ran through the full block editor workflow (create, edit, publish)
• ✅ Checked all active plugins for compatibility errors
• ✅ Reviewed PHP error log for new warnings or fatals
• ✅ Checked browser console for JavaScript errors
• ✅ Verified front-end rendering with your active theme
• ✅ Reported any reproducible bugs to the Alpha/Beta forum or Trac
• ✅ Updated "Tested up to: 7.0" in your plugin/theme readme (if applicable)

Frequently Asked Questions

What is a WordPress Release Candidate (RC)?

It's the final pre-release stage before a stable version ships. All planned features are locked in, major bugs are fixed, and testing shifts to stability and edge cases only.

Is it safe to install WordPress 7.0 RC2 on a live site?

No. RC2 is not production-safe. Install it only on a staging site, a local environment, or WordPress Playground — never on a site that serves real visitors.

What actually changed between RC1 and RC2?

Only bug fixes and stability improvements — no new features. Changes are limited to Gutenberg commits and Trac tickets closed between March 24–26, 2026.

How do I report a bug I find in RC2?

Post to the WordPress.org Alpha/Beta support forum if you're unsure how to write a formal report, or file directly on Trac if you can reproduce it reliably. Check the known-bugs list first to avoid duplicates.

When is WordPress 7.0 scheduled to officially release?

The planned final release date at the time of RC2 was April 9, 2026, pending no further blocking issues from this round of testing.

What are the two most important features to test in RC2?

Real-time collaboration in the block editor, and content-only editing mode for synced block patterns — both flagged as priority testing areas by the core team.

What's Next

Keep an eye on the Make WordPress Core blog and the 7.0 tag for last-minute updates before the final release. If you manage a Joomla site alongside WordPress projects, check our Joomla category for related release-testing coverage.