Understanding the Core Issue Behind the RTC Delay
WordPress recently postponed the release of version 70, a decision that sparked intense discussions among users and developers. The centerpiece of this delay was the RealTime Collaboration (RTC) feature, which enables multiple users to edit content simultaneously within the block editor. While the feature promises transformative utility for publishers and agencies, its instability raised critical questions about its readiness for the core platform.
The delay disrupted the planned rollout of Gutenbergs phase 3, which focuses heavily on collaboration advancements. Critics argue that RTC might not be necessary in the core, pointing to the uneven performance during beta testing. Others see this as indicative of deeper issues in WordPresss development strategy, suggesting fundamental challenges that extend beyond a single feature.
How RTC Has Been Tested and the Results
Since October 2025, RTC has been available for beta testing through Automattics WordPress.com, specifically targeting enterprise-level customers of WordPress VIP. The tests revealed that RTC performs best when paired with native WordPress blocks or custom blocks developed using strict best practices. This finding highlights the importance of adhering to modern standards within the Gutenberg framework.
Stress tests conducted by multiple teams demonstrated RTCs capacity to handle complex editing scenarios. These included adding dozens of blocks simultaneously and copying large volumes of content. Interestingly, testers reported that working on the same post collaboratively was not only functional but enjoyable, showcasing the potential for RTC to revolutionize content creation workflows.
Challenges Encountered During Beta Testing
Despite the promising results under controlled conditions, RTC faced several challenges. The initial approach to storing editing events reused existing database tables, leading to multiple bugs and performance inconsistencies. This design flaw necessitated a shift to a new storage method, causing development delays and fueling skepticism about the features readiness.
The documentation revealed that RTC struggles when used with blocks that deviate from WordPresss best practices. Developers working outside these guidelines encountered compatibility issues, demonstrating the necessity for standardized block design to fully harness RTC's capabilities.
The Broader Implications for WordPress
The delay in version 70 has reignited debates about the direction of WordPress development. Some view the RTC feature as a distraction, questioning whether such advanced functionality belongs in the core. Others believe it represents a bold attempt to keep the platform competitive in an era of increasing collaborative workflows.
More broadly, this incident raises concerns about the sustainability of WordPresss ambitious four-phase Gutenberg roadmap. As the platform grapples with technical hurdles, users and developers alike are left to ponder whether the promise of a richer editing experience is worth the growing pains.
What Comes Next for RTC and WordPress
To address the issues uncovered during beta testing, developers are working to implement a more robust system for storing editing events. This shift is expected to improve RTCs reliability while laying the groundwork for its eventual integration into the core. However, this process will require significant time and resources, potentially delaying other planned features.
Looking ahead, the success of RTC will depend on the collective effort of developers, testers, and users. By adhering to modern standards and embracing the challenges posed by innovation, WordPress has the opportunity to redefine what a content management system can achieve in the realm of collaborative editing. Whether this gamble pays off remains to be seen, but the stakes have never been higher for the platforms future.