WordPress 7.0 Real-Time Collaboration: What It Means for Your Hosting Setup

What Is WordPress 7.0 Real-Time Collaboration?

For fifteen years, WordPress editing has been single-user: one person opens a post, edits it, saves. WordPress 7.0 changes that fundamentally. Real-Time Collaboration (RTC) lets multiple editors work on the same post simultaneously, with changes appearing live for everyone — cursor positions, text insertions, block moves, and all.

The feature is purpose-built for editorial teams, agency workflows, and anyone who has spent time pasting content between Notion, Google Docs, and WordPress to collaborate before publishing. It brings that workflow natively into the block editor.

But collaborative editing isn't just a feature — it's an infrastructure requirement. The hosting implications are significant and, so far, almost entirely absent from the WordPress news cycle. That's the gap this post fills.

Release Status: The Delay Explained

WordPress 7.0 was originally scheduled for April 9, 2026. On March 31, the core team announced it was reverting from Release Candidate back to Beta 3 — a rare step that signals a meaningful technical problem, not a minor polish issue.

The reason: the RTC feature's database architecture. The initial implementation used optimistic locking at the document level, which created merge conflicts and data loss scenarios under concurrent write load (WordPress.org Developer Blog, April 2026). The team switched to a row-level locking approach with a dedicated collaboration session table, but the migration required additional testing before it could be shipped.

The delay is actually good news for site owners: it gives you a window to check your hosting stack before the release lands. Use it.

How RTC Works Under the Hood

Understanding the architecture explains why hosting requirements changed. WordPress 7.0 RTC uses three interconnected mechanisms:

The key implication: RTC is not a JavaScript-only feature. It requires the server to maintain persistent connections and the database to handle concurrent writes correctly. Both are controlled entirely by your hosting environment — not your WordPress theme or plugins.

Hosting Requirements You Need to Check

Four requirements. All of them matter. None of them are optional if you want RTC to actually work.

1. PHP 8.2 or higher

WordPress 7.0 requires PHP 8.2 as a minimum (WordPress.org, 2026). The RTC engine uses named arguments, readonly class properties, and fibers — language features only available from PHP 8.1+, with full stability requiring 8.2+. PHP 8.4 is the recommended version for the best performance.

If your site is still on PHP 7.4 or PHP 8.0, WordPress 7.0 will either refuse to activate RTC features or fail the upgrade entirely. Check your PHP version in your MevoHost control panel under PHP Manager — switching takes about 30 seconds.

// In wp-config.php or via CLI:
php -v

// Minimum for WP 7.0 RTC:
PHP 8.2.x ✓
PHP 8.3.x ✓  (recommended)
PHP 8.4.x ✓  (best performance)

// Will block RTC:
PHP 7.4.x ✗
PHP 8.0.x ✗
PHP 8.1.x ✗  (partial support only)

2. WebSocket or SSE support

The RTC engine needs persistent connections. WebSocket support requires the host to allow HTTP upgrade requests and not forcibly terminate long-lived connections. Many shared hosts cap connection time at 30–120 seconds — enough for a page load, not enough for a live editing session.

Server-Sent Events (SSE) are the fallback — lighter weight and HTTP/1.1 compatible, but still requiring the host to allow persistent open connections without timeout. If both are blocked, RTC degrades to periodic polling, which produces noticeable lag between editors.

3. MySQL 8.0+ or MariaDB 10.6+ with InnoDB

The collaboration session table requires InnoDB with row-level locking enabled. MySQL 8.0 and MariaDB 10.6+ provide this natively. MariaDB 11.x adds further improvements to concurrent transaction handling that benefit the OT session layer directly.

Older MySQL 5.7 installations or MariaDB versions below 10.6 may work for single-user WordPress but will produce lock contention and session corruption under concurrent RTC edits. The March 31 revert was partly triggered by exactly this failure mode in the RC testing environment.

4. Memory headroom per concurrent editor

Each active RTC session requires approximately 32–64 MB of PHP memory per concurrent editor, beyond the baseline WordPress memory allocation (WordPress core team estimates, 2026). A site with five simultaneous editors needs at least 320 MB of PHP memory available — plus the base WordPress footprint of ~128 MB — meaning a PHP memory limit below 512 MB will start causing dropped sessions under real collaborative use.

Will Shared Hosting Handle It?

Mostly no — and for specific technical reasons, not just marketing positioning.

Shared hosting environments pool resources across hundreds of sites on a single server. Persistent WebSocket connections and elevated per-session memory allocations would allow any one site to consume resources that affect every other site on the same host. That's why shared hosts either block WebSocket upgrades outright or enforce aggressive connection timeouts that make RTC unusable in practice.

Single-user WordPress on shared hosting will continue to work fine after the 7.0 upgrade — you just won't be able to activate RTC with colleagues. If you're a solo blogger who never shares post editing, shared hosting is still adequate. But if you're running an editorial team or agency workflow, the RTC feature is the reason to evaluate a hosting upgrade before WordPress 7.0 ships.

What MevoHost Is Doing to Prepare

MevoHost's infrastructure already meets all four WordPress 7.0 RTC requirements on every managed WordPress and VPS plan. Here's the current stack:

WordPress 7.0 Upgrade Checklist for Site Owners

Run through this before WordPress 7.0 ships. Each item takes less than five minutes.

Frequently Asked Questions