Some links on this page are affiliate links. We may earn a commission when you click through and make a purchase, at no additional cost to you.
On May 27, 2026, the WordPress core development team convened on Slack to discuss the latest updates and challenges following the recent release of WordPress 7.0 “Armstrong.” This Dev Chat revealed critical insights about ongoing maintenance, upcoming features in 7.1, and pressing issues affecting site operators, especially those managing custom post types (CPTs) with mixed editor setups.
- WordPress 7.0 “Armstrong” launched with key accessibility improvements, but a few issues are pending a 7.0.1 patch.
- Development for WordPress 7.1 is underway, with active volunteer recruitment and early testing phases focusing on media editor modals, PHP support, and Unicode email enhancements.
- A significant UI inconsistency in the publishing screen affects non-block editor setups, particularly impacting CPTs; a dual-plugin fix approach using Classic Editor and Hotfix plugins is planned.
- Coordination between the core team and plugin maintainers like WP Rocket is accelerating fixes for compatibility and usability concerns.
- Discussions about the new profiles page are ongoing, with community input encouraged ahead of next meetings.
What Happened
The WordPress core team confirmed that WordPress 7.0 “Armstrong” was officially released on May 20, 2026. This release included several developer-focused accessibility improvements such as removing title attributes from author links to enhance screen reader compatibility. The team also published detailed developer notes and field guides to aid the community in adapting to the new version.
Despite the successful launch, some issues remain in the milestone tracker for WordPress 7.0.1. The team debated the urgency of these issues and decided to call for volunteers to target a mid-to-late June release of 7.0.1. This timeline allows for adequate testing and review.
Looking ahead, WordPress 7.1-alpha development is actively progressing. Two major posts announced the commencement of operation WP 7.1 and the call for volunteers. Key focus areas include media editor modal improvements, clarifications on PHP support, and extending Unicode support in emails. Testing and review efforts have begun, aiming to solidify these features before the final release.
A notable discussion centered on a UI problem affecting the publishing screen when the block editor is not in use. This issue particularly impacts CPT workflows, where the publishing interface appears cluttered and confusing. Multiple options were considered for a fix: implementing it directly in the Classic Editor plugin or leveraging the Hotfix plugin for broader coverage.
The team leaned towards a dual-plugin strategy. The Classic Editor plugin, with over 9 million active users, would catch most sites still relying on the classic editing experience and benefit from auto-updates. Simultaneously, the Hotfix plugin—though having a smaller user base—would serve as a stopgap for sites that disable the block editor via hooks or during CPT registration but do not have the Classic Editor plugin active.
Coordination between contributors @jorbin and @desrosj is planned to finalize this approach. Additionally, the Hotfix plugin is slated for a refresh and increased visibility in the WordPress plugin directory to encourage adoption during this interim period.
Further collaboration was noted with third-party plugin maintainers, including WP Rocket, which has already opened a ticket to address the publishing screen issue on their end.
Finally, the conversation touched on the new profiles page, with feedback invited from the community on missing features or usability concerns ahead of the next development chat.
Why This Matters
The recent WordPress 7.0 release marked a significant step forward for accessibility and developer experience, aligning with WordPress’s long-term goals of inclusivity and performance. However, the persistent issues in the publishing interface for non-block editor users underscore a critical challenge within the ecosystem: maintaining smooth workflows across diverse editing configurations.
In real hosting environments and agency operations managing multiple client sites, inconsistent or broken editor interfaces can cause confusion, increase support tickets, and delay content publishing. This is especially true for sites with custom post types that often rely on tailored editor setups. Since a sizable portion of the WordPress ecosystem continues to use the Classic Editor plugin or selectively disable the block editor, any UI breakage impacts a substantial user base.
The proposed dual-plugin fix strategy reflects a pragmatic approach to ecosystem complexity. Relying solely on a core patch would delay relief, while a single-plugin solution risks missing key user scenarios. The Classic Editor plugin’s large installation base provides wide coverage for sites committed to the classic editing experience, while the Hotfix plugin offers a flexible, temporary solution for edge cases without long-term commitment.
From a technical standpoint, this approach also highlights the inherent trade-offs in WordPress’s dual-editor architecture. As the platform transitions towards full site editing and block-based workflows, legacy support remains vital to avoid fragmenting the user community. The maintenance burden is real, and the core team’s coordination with plugin maintainers exemplifies effective ecosystem stewardship.
For agencies and developers, these developments emphasize the need to monitor editor configurations closely during upgrades. Testing sites with CPTs and mixed editor usage is essential to identify UI glitches early. Furthermore, the call for volunteers and ongoing discussions about PHP support and Unicode handling signal that WordPress continues evolving its core capabilities to meet modern development standards and internationalization requirements.
What This Means for WordPress Users
Agencies and site operators should prepare for incremental updates addressing known issues post-7.0 release. Enabling auto-updates for the Classic Editor plugin is a low-friction way to mitigate the publishing screen problem for sites still using the classic editing experience.
For sites that disable the block editor without Classic Editor installed—common in bespoke CPT implementations—installing the Hotfix plugin is advisable until the permanent fix is merged into core. This dual approach ensures that content publishing workflows remain stable and user-friendly.
Developers building custom post types should review their editor registration code and test across WordPress versions 7.0 and upcoming 7.1 to catch any UI inconsistencies early. Engaging with the WordPress community through testing and feedback channels is encouraged, especially as the 7.1 cycle focuses on media editing enhancements and PHP support improvements.
Finally, keeping an eye on the profiles page redesign and participating in feedback rounds can help site operators and developers influence usability improvements that affect author and user management—a critical area for multisite and membership-driven environments.
Frequently Asked Questions
- Q: Should I install the Classic Editor plugin after upgrading to WordPress 7.0?
- A: If your site relies on the classic editing experience or has custom post types that exhibit publishing screen issues, installing or ensuring the Classic Editor plugin is active can prevent UI problems. It also benefits from auto-update facilities.
- Q: What is the Hotfix plugin and when should I use it?
- A: The Hotfix plugin is a temporary patching tool designed to address specific bugs before core releases. Use it if your site disables the block editor but does not have the Classic Editor plugin installed, as it covers edge cases not addressed by the Classic Editor plugin fix.
- Q: Will WordPress 7.1 address the publishing screen issues?
- A: The 7.1 development is focused on new features and improvements like media editor modals and PHP support. The publishing screen bug fix is planned as a 7.0.1 release and via plugin patches rather than part of 7.1.
- Q: How can I participate in WordPress 7.1 development?
- A: Volunteer calls are open until early June. You can join testing efforts, review tickets, and contribute code or feedback via the Make WordPress Core channels and Trac.
- Q: Are there any risks to applying the Hotfix or Classic Editor plugin fixes?
- A: Both plugins are well-maintained and widely used. However, always test updates on staging environments first, especially for sites with custom workflows or complex CPT setups, to avoid unexpected conflicts.
