WordPress 7.0 Release Candidate 2 is here — the final pre-release checkpoint before the official launch. Here's everything you need to know about testing it, what changed since RC1, and how to get involved before the April 9, 2026 release date.
What Is a WordPress Release Candidate?
A Release Candidate (RC) is the last phase of the WordPress release cycle before the final, stable version ships. By this point, all planned features are in, major bugs are resolved, and the focus shifts entirely to stability verification and edge-case testing.
RC2 specifically means that issues were found in RC1, addressed, and now a second round of broad testing is needed before the team is confident enough to tag the release as final. Think of it as 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 you can test RC2, you need a safe sandbox. You have four options depending on your setup and technical comfort level:
- WordPress Beta Tester Plugin — Install and activate the WordPress Beta Tester plugin on an existing WordPress site. In the plugin settings, choose the Bleeding Edge channel and the Beta/RC Only stream. This is the easiest method if you already have a test site.
- Direct Download — Download the RC2 zip file from WordPress.org and install it manually on a staging server. This gives you full control over the environment.
-
WP-CLI — If you manage WordPress from the command line, run:
wp core update --version=7.0-rc2. Fastest method for developers who are already SSH'd into a test server. - WordPress Playground — No server needed. Open the WordPress Playground instance directly in your browser. Perfect for quick feature testing without any setup overhead.
Step 2 — Know What to Test in WordPress 7.0
The RC2 testing focus is on stability, not discovery. That said, WordPress 7.0 ships with significant new capabilities that benefit from real-world testing across diverse environments. The two priority areas flagged by the core team are:
Real-Time Collaboration
WordPress 7.0 introduces real-time co-editing in the block editor. Multiple users can now 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, meaning editors can update text and images inside a pattern without accidentally breaking its underlying structure. Test by creating synced patterns, entering content-only mode, making edits, and verifying the pattern structure stays intact across pages where it's used.
Step 3 — Review What Changed Since RC1
RC2 is a targeted update, not a feature addition. All changes since RC1 (tagged on March 24, 2026) are bug fixes and stability improvements. The two best ways to dig into specifics:
- GitHub Commits — Browse the Gutenberg commits between March 24–26, 2026 to see exactly which block editor changes landed in RC2.
- Trac Tickets — Review the closed Trac tickets from the same window for core PHP/JS fixes. Filter by component to focus on areas relevant to your plugins or themes.
If you tested RC1 and reported an issue, this is the right time to verify whether your reported bug appears in the closed tickets list — and re-test if it does.
Need a reliable staging environment for WordPress testing?
Recommended Hosting — Testing WordPress release candidates requires an isolated environment where you can install, break, and reset freely. A quality managed hosting plan gives you one-click staging sites, PHP version control, and WP-CLI access — everything you need to run RC2 safely.
Find a Staging-Ready Host →
Step 4 — Report Issues the Right Way
Found something broken? How you report it matters. Here's where to go depending on your comfort level:
- Support Forums (Alpha/Beta area) — Post to the Alpha/Beta forum if you've found an issue but aren't sure how to write a formal bug report. Describe the steps to reproduce, your environment (PHP version, active plugins, theme), and what you expected vs. what happened.
- WordPress Trac — File directly on Trac if you can write a reproducible report. Check the known bugs list first to avoid duplicates.
-
Core Test Slack — Join the
#core-testchannel on Making WordPress Slack for real-time discussion with the testing team.
Bonus Tip: 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 will start updating, and any incompatibilities become user-facing problems.
The most important action: update the Tested up to field in your plugin's readme.txt to 7.0 once you've confirmed compatibility. This signals to users on WordPress.org that your plugin is ready for the new version. If you find a compatibility issue, post details to the Alpha/Beta support forum.
Troubleshooting Common RC2 Issues
Testing release candidates can surface environment-specific problems that aren't bugs in WordPress itself. Before filing a report, check these common causes:
| 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 env-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 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)
Conclusion
WordPress 7.0 RC2 represents the final stretch before one of the platform's most significant releases in recent years. Real-time collaboration and the refined pattern editing system are features that will change how editorial teams use WordPress day-to-day — and the stability of those features at launch depends on how thoroughly they get tested now.
The final release is scheduled for April 9, 2026. Every hour of testing between now and then contributes directly to the quality of the release that millions of sites will update to. Whether you test for five minutes on WordPress Playground or spend an afternoon running your plugin's full test suite, it counts.
Check the Make WordPress Core blog and the 7.0 tag for any last-minute updates before the final release drops.
