WordPress 7.1.1 Release Candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 (RC1) is available for testing! Some ways you can help test this minor release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.:
- Use the WordPress Beta Tester plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
- As this is a minor RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release, select the Point Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..
- Use WP-CLI to test: wp core update https://wordpress.org/wordpress-7.1.1-RC1.zip
- Directly download the Beta/RC version.
What’s in this release candidate?
WordPress 7.1.1 is intended as a bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 7.1 cycle or intentionally deferred at the end of the 7.1 cycle. You can follow trac report 4 or the 7.1.x editor tasks board for proposed fixes.
WordPress 7.1.1 is led by @adamsilverstein, @adrianduffell, and @andraganescu.
The following core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets are included:
- #66001 – Accessing /wp-admin (and super admin)/admin-post.php?page=font-library while logged loads Site Editor
- #65929 – Block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Supports: Bail early in wp_render_block_states_support() when a block has no style attribute
- #65674 – Tooltip Delay Timer Race Condition (wp-includes/js/wp-tooltip.js)
- #65943 – wp-tooltip 7.1 bug
- #65914 – wp_get_tooltip() treats custom button markup as a sprintf() format string
- #65918 – Tooltip icon is not aligned with “Remember Me” text in login box
- #66056 – Media: prepare the attachment finalize response from the current post row
- #65922 – regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.: client-side processing creates thumbnails larger than original for indexed PNG images
- #66012 – Multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site: reassign dropdown missing when deleting a user, silently destroying content (7.1 regression)
- #65919 – Array keys in WP_Hook::$callbacks may now be integers instead of strings in 7.1 causing fatal errors with string functions
- #65985 – Plugins: In < 782px screens paused plugins has two left borders
- #65956 – Mobile layout breaks on post list table during plugin update
- #65945 – Native sitemap is served with a 404 status on sites with no published posts
- #66044 – spacing.blockGap in a block style variation stops emitting any gap
- #66064 – Site icon in the Admin Bar (Toolbar) sits atop the site title when using a tablet in portrait orientation
- #65924 – Set Site Icon background color to transparent
The following Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/ PRs are included:
- #81770 – Block Editor: Add translator context to pseudo-state labels
- #81813 – Fix: Post Editor: 403 on /wp/v2/settings at boot for users without manage_options cap
- #82046 – Media: Refuse a multi-file drop on a placeholder that takes one file
- #82011 – List: outdent an empty middle item without adding an item
- #81782 – Accordion Panel: Reset padding-block when panel is hidden
- #81964 – List View: Don’t focus the last Table cell on keyboard activation
- #81397 – Media: Stop claiming “Upload complete” when every upload failed
- #81884 – Media: keep indexed PNG sub-sizes indexed
- #82316 – Image block cropping: Sync image size and link destination settings
- #82318 – Gallery block: Fix ‘Crop images to fit’ broken in editor
- #82254 – Pages: require authentication and a capability A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the
current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). to render generated standalone pages
- #82353 – Media Utils: Preserve arrays in multipart form data
- #82478 – wp-env: Fix Docker build errors with Debian Bullseye repositories
- #82465 – Query Loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop: Fall back to
post when the query has no postType
- #81908 – Block Supports: Bail early in state styles when a block has no style attribute
- #82335 – Fix: Restore layout styles for block style variations
- #81947 – Editor: Store the finalize response as the attachment record
- #82265 – Media: Only blame the browser’s codecs when HEIC really cannot be decoded
- #82249 – CI: Unify the automation comments into a single PR comment
- #82183 – useViewConfig: don’t request the view config twice
- #82635 – Framework: Update Node.js to v24 LTS and npm to v11
What’s next?
Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 7.1 branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
The final release is expected on Thursday, September 17, 2026. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in the WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ #7-1-release-leads channel, and releases are always packaged and tested in #core.
A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 7.1.1 depends on proper testing, so please lend a helping hand.
Thanks to @andraganescu and @adamsilverstein for pre-publication review.
#7-1, #7-1-1, #minor-releases, #release
You must be logged in to post a comment.