WordPress 7.1.1 RC1 Release Guide: Critical Bug Fixes, Block Editor Updates, and Testing Workflows

Introduction to WordPress 7.1.1 RC1 and Release Objectives

WordPress 7.1.1 Release Candidate 1 (RC1) marks the first testing build for the upcoming 7.1.1 minor maintenance release. Led by release leads @adamsilverstein, @adrianduffell, and @andraganescu, this release focuses exclusively on resolving bugs introduced during the primary 7.1 cycle or intentionally deferred during its final stages. As a point release, 7.1.1 introduces no new features, concentrating instead on stabilizing Core APIs, Gutenberg block behaviors, admin UI layouts, and media handling routines.

With a target general release date scheduled for Thursday, September 17, 2026, the testing phase for RC1 provides developer teams and site administrators an opportunity to validate fixes across staging environments before deployment to production networks.

Testing Instructions: Plugin, WP-CLI, and Direct Downloads

Testing RC1 requires configuring environment update streams to capture point release nightlies. Developers and QA engineers can evaluate the RC1 build using three standard methods:

• WordPress Beta Tester Plugin: Install the plugin on a non-production site. Navigate to settings, select the Point Release channel, and choose the Nightlies stream. This stream pulls the latest commits in Subversion trunk alongside the RC build.
• WP-CLI Update Command: Execute the core update command via terminal to fetch the packaged zip file directly:

wp core update https://wordpress.org/wordpress-7.1.1-RC1.zip

• Direct Archive Download: Download the wordpress-7.1.1-RC1.zip archive directly from the WordPress.org release distribution path for manual file deployment.

Critical PHP & API Fixes in WP Core

WordPress 7.1.1 addresses several regressions in PHP execution paths and core API helper functions that caused runtime exceptions or unexpected UI redirection.

• WP_Hook Callback Types (#65919): In WordPress 7.1, array keys inside WP_Hook::$callbacks were occasionally stored as integers rather than strings. This introduced fatal errors when custom code or core hooks executed native string functions against hook keys. RC1 enforces valid key string cast expectations across hook arrays.
• Font Library Redirection (#66001): Authenticated users navigating directly to /wp-admin/admin-post.php?page=font-library inadvertently triggered the Site Editor interface. RC1 corrects request routing for the font library page within admin-post contexts.
• Tooltip Helper API (#65914, #65943, #65674): Fixes were applied to wp-includes/js/wp-tooltip.js to resolve a race condition in the tooltip delay timer. Furthermore, wp_get_tooltip() previously treated custom button HTML markup as a sprintf() format specifier, triggering string formatting failures when unescaped percent signs or markup tags were passed.
• Sitemap 404 Status (#65945): Resolved a condition where native Core XML sitemaps were served with an HTTP 404 status header on fresh or empty sites that contained zero published posts.

Media & Attachment Handling Improvements

Media processing pipeline updates address image resizing regressions, upload error handling, and file codec evaluations across Core and the Gutenberg media utils package.

• Indexed PNG Sub-sizes (#65922, #81884): Addresses a 7.1 regression where client-side and server-side image processing generated scaled thumbnail assets larger in file size than original indexed PNG images. Sub-sized assets now retain their indexed color space properties during generation.
• Attachment Finalize Data (#66056, #81947): Core attachment updates now prepare the final response payload directly from the current post database row and persist this finalized structure directly back to the attachment record.
• Multi-file Drop & Upload Error Feedback (#82046, #81397): The editor interface now rejects multi-file drag-and-drop actions onto placeholders designed for single-file inputs. Additionally, media components no longer display an “Upload complete” notification when every file in a batch upload fails.
• Codec & HEIC Detection (#82265): Adjusts decoder fault attribution so browser media codecs are only flagged when HEIC format images genuinely fail decoding routines.

Block Editor, Styling, and Layout Fixes

Core block supports and style variation processing receive targeted optimizations to reduce unnecessary DOM evaluation overhead and eliminate broken layout calculations.

• Block Supports Early Bail (#65929, #81908): Refactored wp_render_block_states_support() and state styles handling to bail early whenever an evaluated block lacks a style attribute, preventing unnecessary style array iteration.
• Block Gap & Variation Layouts (#66044, #82335): Resolved an issue where spacing.blockGap within block style variations ceased emitting CSS gap definitions. Layout styles for custom variations are fully restored.
• Image Cropping & Link Sync (#82316, #82318): Synced image size selections and link destination attributes during Image block cropping operations, and fixed the ‘Crop images to fit’ editor toggle within Gallery blocks.
• List Block & Keyboard Navigation (#82011, #81964): Outdenting an empty middle list item now works without inserting an extraneous list node. Keyboard activation in List View no longer forcefully shifts focus to the final table cell.
• Accordion Panel Padding (#81782): Resets the CSS padding-block property whenever an Accordion Panel enters a hidden state.

Admin UI, Mobile Responsiveness, and Multisite Content Protection

Admin list tables and network administration contexts receive interface fixes targeting mobile viewports, toolbar elements, and user deletion routines.

• Multisite User Deletion Regression (#66012): Fixed a severe 7.1 regression in Multisite networks where deleting a user omitted the content reassignment dropdown menu. This flaw caused silent content deletion across network subsites when removing users without explicitly reassigning post ownership.
• Mobile Plugin Table Layout (#65956, #65985): Corrected a broken layout on the main post list table during inline plugin updates on mobile screen widths. Additionally, resolved duplicate left border styling rendering on paused plugins at viewports under 782px.
• Toolbar Site Icon Rendering (#66064, #65924): Fixed an alignment bug on tablet portrait viewports where the site icon in the Admin Bar overlayed the site title text. Set default site icon background colors to transparent to prevent solid background fill conflicts.

REST API, Security Controls, and Developer Environment Upgrades

Developer tooling and REST endpoint capabilities have been updated to enforce appropriate permissions and modernize the development toolchain.

• REST API Permission Checks (#81813, #82254): The Post Editor boot process no longer throws a 403 Forbidden error on /wp/v2/settings for users lacking the manage_options capability. Furthermore, generated standalone pages now explicitly enforce authentication and capability checks prior to rendering.
• Query Loop Fallback (#82465): When a Query Loop block context carries no explicit postType parameter, the query logic gracefully falls back to the default post type.
• Multipart Form Data Arrays (#82353): Media utility functions now preserve nested array structures when constructing multipart/form-data requests.
• Toolchain Upgrades (#82478, #82635): Resolved Docker build failures within wp-env stemming from deprecated Debian Bullseye repositories. Core build frameworks upgraded to Node.js v24 LTS and npm v11.

Release Management, Branching Strategy, and Next Steps

To preserve branch stability leading up to the final September 17, 2026 release, core contributors must follow strict committer workflows:

• Dev-Reviewed Workflow: All proposed commits targeting the 7.1 release branch require mandatory double committer sign-off (dev-reviewed workflow) before merging.
• Bug Tracker Tracking: Pending candidate patches and reported bugs can be reviewed directly on Trac Report 4 or the official 7.1.x Editor Tasks board.
• Release Coordination: Development discussion and release packaging coordination take place in the #7-1-release-leads and #core Slack channels.

Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.