WordPress co-founder Matt Mullenweg has proposed delaying the release of WordPress 7.0 to prioritize the development of a critical feature: real-time collaboration (RTC). Originally scheduled for a live release during Contributor Day at WordCamp Asia 2026, Mullenweg announced his decision in the #core-committers channel on WordPress Slack, citing the need for foundational changes to the database structure to support RTC.
Key Takeaways
- Matt Mullenweg has proposed delaying WordPress 7.0 to focus on real-time collaboration (RTC).
- The delay centers on introducing a new database table to support RTC functionality.
- WordPress 7.0 was originally slated for release at WordCamp Asia 2026 Contributor Day.
- This marks a significant shift in priorities for the WordPress core team.
- The delay signals the importance of foundational architectural changes for future WordPress features.
Why WordPress 7.0 Is Being Delayed
The decision to delay WordPress 7.0 comes as no surprise to developers closely following its progress. Real-time collaboration has long been a feature discussed within the WordPress ecosystem, but its implementation requires significant architectural changes. The core issue lies in the database structure that WordPress uses, which has remained largely unchanged since its inception. Mullenweg emphasized that building RTC without introducing a dedicated database table would compromise the feature’s performance and scalability.
Real-time collaboration tools allow multiple users to edit content simultaneously while viewing changes in real-time. Popularized by platforms like Google Docs, RTC has become a high-demand feature for teams and agencies that rely on WordPress for content creation. According to Mullenweg, the delay ensures the functionality will be “future-proof and performant,” paving the way for more advanced collaborative workflows in WordPress.
The Technical Challenge: Database Tables for RTC
WordPress’s database architecture has historically relied on MySQL tables optimized for blog posts, comments, and media storage. However, real-time collaboration introduces new technical requirements, such as frequent reads and writes, session management, and conflict resolution. These operations demand a specialized table structure capable of handling high volumes of concurrent data transactions.
In practice, implementing RTC involves creating a dedicated table to store revision data, user sessions, and lock states. This table would act as a central hub for tracking real-time changes. Without such foundational support, RTC would struggle to deliver responsive performance, especially on high-traffic sites or multisite networks.
Previous attempts to introduce similar features have highlighted the limitations of the existing database schema. For example, the WordPress autosave functionality, while useful, often struggles under heavy load. Expanding this concept to RTC would exacerbate those challenges without a re-engineered approach.
Community Reaction
The announcement has sparked a mixed reaction within the WordPress community. While many developers and agencies support the delay, citing the importance of architectural stability, others have expressed concerns about missed deadlines and the impact on adoption rates. Contributor Day at WordCamp Asia was expected to be a showcase moment for WordPress 7.0, and the delay may dampen enthusiasm among contributors.
However, seasoned developers see this as a necessary trade-off. “You can’t rush foundational changes,” one core contributor commented. “Adding a feature like RTC without proper infrastructure would create more problems down the line.”
What This Means for WordPress Users
For WordPress users, especially agencies and businesses that rely on collaborative workflows, the delay signals a promising investment in the future of the platform. Real-time collaboration has the potential to transform WordPress into a more competitive tool in enterprise environments, where collaboration and efficiency are paramount.
Developers should prepare for upcoming changes to the database schema, which may require adjustments to custom plugins or themes that interact directly with the database. Agencies should communicate the importance of these architectural improvements to clients, emphasizing the long-term benefits.
From a strategic perspective, this move highlights WordPress’s commitment to evolving beyond its blogging roots. As the platform grows to accommodate more complex use cases, foundational changes like the ones proposed for RTC become essential.
Frequently Asked Questions
What is real-time collaboration (RTC)?
Real-time collaboration allows multiple users to edit content simultaneously, with changes visible in real-time, similar to Google Docs.
When will WordPress 7.0 be released?
No updated release date has been announced yet, as the focus is now on developing RTC and its supporting database table.
Will this delay affect other planned features?
It’s unclear, but major development efforts will likely center around RTC, potentially deprioritizing smaller features.
How will the new database table impact existing plugins?
Plugins interacting directly with the database may need updates to accommodate schema changes introduced for RTC.
