WordPress 7.1 Field Guide  🔗 **Source:** [WordPress 7.1 Field Guide](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/) > [!note]+ Document Notes > --- > tags: [wordpress-core, wordpress-7-1, developer-notes, release-preparation, block-editor, backward-compatibility] > author: Milana Cap > source: Make WordPress Core > reference: https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > --- > # 🏷️ Title: WordPress 7.1 Field Guide > ## 🧭 Table of Contents > - [📝 Summary](#-summary) > - [📖 Main Content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action Items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future Research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning Styles Assessment](#-learning-styles-assessment) > - [📊 Accessibility Assessment](#-accessibility-assessment) > - [🌍 DEIB Assessment](#-deib-assessment) > - [✅ Logical Validity](#-logical-validity) > - [🛡️ DARVO Analysis](#-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > ### 🔗 References > - [WordPress 7.1 Field Guide](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/) > - [WordPress 7.1 release schedule](https://make.wordpress.org/core/7-1/) > ## 📝 Summary > - WordPress 7.1 includes more than 310 closed Core Trac tickets, including over 100 enhancements and feature requests and more than 180 bug fixes. The guide also counts almost 600 Gutenberg enhancements and more than 630 Gutenberg bug fixes. > - Major developer-facing areas include client-side media processing, accessibility, the Abilities API, Global Styles, the SVG Icon API, DataViews and DataForm, the iframed editor, design-system theming, the persistent admin bar, and updated external libraries. > - Plugin and theme developers are the main risk owners because several changes alter editor document boundaries, REST schema output, media behavior, toolbar navigation, component behavior, and third-party dependency expectations. > - The guide names deferred work as carefully as shipped work: React 19, real-time collaboration, the On This Day widget, and broader merge proposals aren't part of WordPress 7.1. > - Bottom line: treat the field guide as the official compatibility map, then test each relevant dev note against a pinned 7.1 release candidate or final build. > ## 📖 Main Content > - The guide is a release-routing document. It groups changes by developer impact and points to dev notes, Trac tickets, and Gutenberg work for implementation details. > - Media work moves supported image operations into the browser before upload and expands REST support for dimension checks, quality choices, and registering one sideloaded file across image sizes. Infinite scrolling becomes the Media Library grid default, with a per-user opt-out. > - Accessibility work changes list-table semantics, introduces a shared accessible tooltip mechanism, and improves focus, contrast, keyboard, pointer, setup, widget, navigation, and editor behavior. > - The Abilities API gains filtered discovery, execution lifecycle hooks, a unified public exposure flag, client-compatible JSON Schema preparation, and smaller refinements. These changes affect both server registration and external clients. > - Editor work includes new block supports, editable supported blocks inside Custom HTML preview, and completion of the iframe-based post editor even when legacy meta boxes exist. Plugins that reach across the editor document boundary must test JavaScript and CSS assumptions. > - The release also adds design-system theming foundations, keeps the toolbar present through supported editor navigation, and updates jQuery UI to 1.14.2. > - Release counts and dev notes describe scope, not runtime proof. A target build, fixtures, and observed results are still required before claiming compatibility. > ### 🗒️ Notes > - The field guide was published during the release-candidate phase and targets extenders, Core developers, and others tracking WordPress development. > - Its ticket and line-change counts communicate size but don't measure risk. One boundary change can matter more to a plugin than hundreds of unrelated fixes. > - Client-side media processing shifts part of the upload pipeline into the browser. Test format support, large images, failed transforms, sideload registration, and server fallback behavior. > - Media Library infinite scrolling changes the default browsing pattern. Test keyboard movement, screen-reader announcements, large libraries, selection state, and the per-user opt-out. > - Accessible tooltips replace title-attribute and pointer-only patterns with a shared convention. Test naming, description, focus order, escape behavior, hover, touch, and zoom. > - Changed row headers improve list-table semantics but may expose brittle selectors or custom-column assumptions. > - The Abilities API public flag and JSON Schema preparation are linked concerns: discovery must match exposure policy, and exposed schemas must remain consumable by clients. > - Global Styles gains responsive variations, configurable viewports, more interaction states, and text shadow. Theme authors should test serialization, inheritance, presets, and editor/front-end parity. > - The SVG Icon API creates a standard registration and rendering path. Check escaping, accessible names, view boxes, theming, and duplicate identifiers. > - DataViews, DataForm, and View Config continue to change. Extensions should test supported views and layouts instead of depending on internal component shape. > - The enforced editor iframe is the highest-risk boundary change for extensions that query the parent document, inject global CSS, bind document-level events, or assume meta boxes disable iframe mode. > - Persistent toolbar navigation raises lifecycle questions for extensions during client-side navigation: mount, unmount, state reset, and stale handlers. > - jQuery UI 1.14.2 needs focused regression tests for plugins that depend on its interaction behavior or styling. > - The guide correctly records exclusions. React 19 and real-time collaboration remain outside the shipped 7.1 scope, so they shouldn't appear in compatibility claims for this release. > ## 📚 References > - [WordPress 7.1 Field Guide](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/) > - [Client-Side Media Processing in WordPress 7.1](https://make.wordpress.org/core/2026/07/22/client-side-media-processing-in-wordpress-7-1/) > - [Post list tables row headers changed](https://make.wordpress.org/core/2026/08/03/post-list-tables-row-headers-changed/) > - [Introducing name and informational tool tips in WordPress 7.1](https://make.wordpress.org/core/2026/08/03/introducing-name-and-informational-tool-tips-in-wordpress-7-1/) > - [A unified public exposure flag for Abilities in WordPress 7.1](https://make.wordpress.org/core/2026/08/04/a-unified-public-exposure-flag-for-abilities-in-wordpress-7-1/) > - [JSON Schema preparation for client compatibility in WordPress 7.1](https://make.wordpress.org/core/2026/07/31/json-schema-preparation-for-client-compatibility-in-wordpress-7-1/) > - [Iframed Editor Changes in WordPress 7.1](https://make.wordpress.org/core/2026/08/03/iframed-editor-changes-in-wordpress-7-1/) > - [Miscellaneous Editor Changes in WordPress 7.1](https://make.wordpress.org/core/2026/08/04/miscellaneous-block-editor-changes-in-wordpress-7-1/) > - [React 19: punted beyond WordPress 7.1](https://make.wordpress.org/core/2026/07/24/react-19-punted-beyond-wordpress-7-1-experiment-in-gutenberg/) > ## 🗣️ Paraphrase > WordPress 7.1 is broad, but the practical developer story is a set of changed boundaries: more media work happens in the browser, accessibility semantics are stricter, abilities are easier to expose to clients, style and data APIs expand, and the post editor consistently lives in an iframe. > The safest response isn't to scan the ticket count and assume compatibility. Map each product's integration points to the linked dev notes, run controlled tests on a pinned build, and keep deferred experiments out of 7.1 claims. > ## 📰 Newsletter > WordPress 7.1's Field Guide is the compatibility map worth keeping beside your test plan. The release touches media processing, accessible admin patterns, the Abilitie This guide outlines major developer features and breaking changes in 7.1 and is published during the Release Candidaterelease 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)](#alpha-beta). phase to help inform WordPress extenders, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. developers, and everyone else interested in the latest WordPress development. There are more than [310 Core Trac tickets](https://core.trac.wordpress.org/query?milestone=7.1&status=closed&group=component&order=priority&col=id&col=summary&col=type&col=focuses) included in WordPress 7.1, over [100 of which are enhancements and feature requests](https://core.trac.wordpress.org/query?milestone=7.1&status=closed&type=enhancement&type=feature+request&group=component&max=200&order=priority&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority), and [more than 180 bug fixes](https://core.trac.wordpress.org/query?milestone=7.1&status=closed&type=defect+(bug)&group=component&max=500&order=priority&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority). This release includes [40+ tickets focused on the Editor](https://core.trac.wordpress.org/query?component=Editor&milestone=7.1&status=closed&order=priority&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority), with the most attention going to accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) ([46](https://core.trac.wordpress.org/query?focuses=~accessibility&milestone=7.1&status=closed&group=component&order=priority&col=id&col=summary&col=focuses&col=type&col=keywords)), UIUI User interface ([40](https://core.trac.wordpress.org/query?focuses=~ui&milestone=7.1&status=closed&group=component&order=priority&col=id&col=summary&col=focuses&col=type&col=keywords)), and administration ([28](https://core.trac.wordpress.org/query?focuses=~administration&milestone=7.1&status=closed&group=component&order=priority&col=id&col=summary&col=focuses&col=type&col=keywords)) focuses. Additionally, this release includes almost [600 enhancements](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Enhancement%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2022.7%22%20OR%20milestone%3A%22Gutenberg%2022.8%22%20OR%20milestone%3A%22Gutenberg%2022.9%22%20OR%20milestone%3A%22Gutenberg%2023.0%22%20OR%20milestone%3A%22Gutenberg%2023.1%22%20OR%20milestone%3A%22Gutenberg%2023.2%22%20OR%20milestone%3A%22Gutenberg%2023.3%22%20OR%20milestone%3A%22Gutenberg%2023.4%22%20OR%20milestone%3A%22Gutenberg%2023.5%22%20OR%20milestone%3A%22Gutenberg%2023.6%22)) and [more than 630 bug fixes](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Bug%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2022.7%22%20OR%20milestone%3A%22Gutenberg%2022.8%22%20OR%20milestone%3A%22Gutenberg%2022.9%22%20OR%20milestone%3A%22Gutenberg%2023.0%22%20OR%20milestone%3A%22Gutenberg%2023.1%22%20OR%20milestone%3A%22Gutenberg%2023.2%22%20OR%20milestone%3A%22Gutenberg%2023.3%22%20OR%20milestone%3A%22Gutenberg%2023.4%22%20OR%20milestone%3A%22Gutenberg%2023.5%22%20OR%20milestone%3A%22Gutenberg%2023.6%22)), coming from GutenbergGutenberg 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/>. A quick search of the diff between 7.0.2 and the current trunktrunk 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. (7.1-beta4) reveals 20 new hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. (19 filters and 1 action), 1480 total files changed with 88163 insertions and 18601 deletions. Kudos to everyone who contributed to the 7.1 release, in any way, shape, or form. Below is a breakdown of the most important developer-related changes included in WordPress 7.1. 1. [Media](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#media) 1. [Client-side media processing](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#client-side-media-processing) 2. [Media library](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#media-library) 2. [Accessibility](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#accessibility) 1. [Administration](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#administration) 2. [Accessible tooltips in core](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#accessible-tooltips-in-core) 3. [Abilities API](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#abilities-api) 4. [Global styles](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#global-styles) 5. [SVG Icon API](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#svg-icon-api) 6. [DataViews, DataForm, and View Config APIs](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#dataviews-dataform-and-view-config-apis) 7. [Editor](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#editor) 1. [New Block Support](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#new-block-support) 2. [Enforced iframed editor](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#enforced-iframed-editor) 3. [Editor components](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#editor-components) 8. [Design System](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#design-system) 9. [Persistent Admin Bar](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#persistent-admin-bar) 10. [External libraries](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#external-libraries) 11. [Other updates](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#other-updates) 12. [But wait, there’s more!](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#but-wait-there-s-more) 13. [What changes didn’t make the 7.1 release](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#what-changes-didn-t-make-the-7-1-release) 1. [Classic block](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#classic-block) 2. [Real-time collaboration](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#real-time-collaboration) 3. [“On This Day” widget](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#on-this-day-widget) 4. [Merge proposals](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#merge-proposals) #### Media WordPress 7.1 continues the modernisation of media workflows across the editor, REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) <https://developer.wordpress.org/rest-api/>, and Media Library. The release introduces client-side processing capabilitiescapability 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)., improves the handling and registration of image sizes, and changes the default Media Library browsing experience. ##### Client-side media processing New client-side media processing APIs allow supported image operations to happen in the browser before a file is uploaded. Related REST API changes support validating image dimensions, selecting size-aware encoding quality, and registering a sideloaded file for multiple image sizes. > [Client-Side Media Processing in WordPress 7.1](https://make.wordpress.org/core/2026/07/22/client-side-media-processing-in-wordpress-7-1/) Related tickets: * [#64798](https://core.trac.wordpress.org/ticket/64798) — REST API: Add dimension validation to sideload endpoint * [#65262](https://core.trac.wordpress.org/ticket/65262) — REST API: expose size-aware encode quality on attachment responses * [#65481](https://core.trac.wordpress.org/ticket/65481) — REST API: Support registering one sideloaded file under multiple image sizes ##### Media library Infinite scrolling is enabled by default in the Media Library grid, with a per-user option to restore the previous pagination behaviour. The release also includes fixes for upload counts, duplicate caption IDs, and other media-management details. > [Media Library infinite scrolling is now enabled by default, with a per-user opt-out](https://make.wordpress.org/core/2026/07/23/media-library-infinite-scrolling-is-now-enabled-by-default-with-a-per-user-opt-out/) Other media changes: * [#65053](https://core.trac.wordpress.org/ticket/65053) – Correct the media-upload count when uploading multiple files from the post editor * [#65315](https://core.trac.wordpress.org/ticket/65315) – Prevent duplicate figcaption IDs when the same image has different captions #### Accessibility WordPress 7.1 includes accessibility improvements across administration screens, list tables, setup flows, widgets, navigation, and editor-related interfaces. The changes improve semantics, keyboard and pointer interaction, focus behaviour, contrast, and the presentation of contextual information. ##### Administration Administration improvements make hierarchical relationships and table structure clearer to assistive technologies. They also refine focus behaviour, controls, contrast, and interaction patterns across several screens. > [Post list tables row headers changed](https://make.wordpress.org/core/2026/08/03/post-list-tables-row-headers-changed/) ##### Accessible tooltips in core WordPress 7.1 introduces a shared mechanism for accessible name and informational tooltips. Core now uses this mechanism in selected interfaces, giving developers a consistent pattern for presenting supplementary information without relying on inaccessible title attributes or pointer-only interactions. > [Introducing name and informational tool tips in WordPress 7.1](https://make.wordpress.org/core/2026/08/03/introducing-name-and-informational-tool-tips-in-wordpress-7-1/) * [#51006](https://core.trac.wordpress.org/ticket/51006) — Add a mechanism for accessible tooltips in core * [#55343](https://core.trac.wordpress.org/ticket/55343) — Add Tooltip to “Remember Me” (WP Login Form) * [#50921](https://core.trac.wordpress.org/ticket/50921) — Consider adding tooltips for metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. order buttons Other accessibility improvements: * [#64932](https://core.trac.wordpress.org/ticket/64932) – Make subpage hierarchy in post list tables accessible. * [#65027](https://core.trac.wordpress.org/ticket/65027) – Add IDs to section titles generated by the Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. * [#65250](https://core.trac.wordpress.org/ticket/65250) – Correct mouse interaction for the first submenu item when “Collapse Menu” is enabled * [#65382](https://core.trac.wordpress.org/ticket/65382) – Improve adminadmin (and super admin) colour scheme contrast for the editor chrome. * [#65454](https://core.trac.wordpress.org/ticket/65454) – Improve accessibility of setup-config.php and install.php * [#47670](https://core.trac.wordpress.org/ticket/47670) – Fix the accessibility problem caused by multiple RSS widgets * Improving visibility, contrast, layout, and overall accessibility in [#65419](https://core.trac.wordpress.org/ticket/65419), [#65530](https://core.trac.wordpress.org/ticket/65530), [#65532](https://core.trac.wordpress.org/ticket/65532), [#65630](https://core.trac.wordpress.org/ticket/65630) and more. #### Abilities API WordPress 7.1 builds on the Abilities API introduced in WordPress 6.9, making abilities easier to discover, expose, validate, and integrate with external clients. The release adds filtering to `wp_get_abilities()`, execution lifecycle hooks, a unified `public` exposure flag, client-compatible JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. Schema preparation, and several smaller API refinements. > [JSON Schema preparation for client compatibility in WordPress 7.1](https://make.wordpress.org/core/2026/07/31/json-schema-preparation-for-client-compatibility-in-wordpress-7-1/) > [Filtering registered abilities with wp\_get\_abilities() in WordPress 7.1](https://make.wordpress.org/core/2026/08/05/filtering-registered-abilities-with-wp_get_abilities-in-wordpress-7-1/) > [New execution lifecycle filters for the Abilities API in WordPress 7.1](https://make.wordpress.org/core/2026/07/29/new-execution-lifecycle-filters-for-the-abilities-api-in-wordpress-7-1/) > [A unified public exposure flag for Abilities in WordPress 7.1](https://make.wordpress.org/core/2026/08/04/a-unified-public-exposure-flag-for-abilities-in-wordpress-7-1/) > [Abilities API improvements in WordPress 7.1](https://make.wordpress.org/core/2026/07/31/abilities-api-improvements-in-wordpress-7-1/) #### Global styles WordPress 7.1 expands the styling tools available to blockBlock 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. and theme developers, with responsive style variations, configurable viewports, additional interaction states, and text-shadow support. These changes give themes and blocks more expressive styling options while keeping their configuration within the Global Styles system. > [Responsive block styles and configurable viewports in WordPress 7.1](https://make.wordpress.org/core/2026/08/05/responsive-block-styles-and-configurable-viewports-in-wordpress-7-1/) > [Pseudo and custom style states in WordPress 7.1](https://make.wordpress.org/core/2026/08/05/pseudo-and-custom-style-states-in-wordpress-7-1/) > [Text Shadow Support in Global Styles](https://make.wordpress.org/core/2026/07/23/text-shadow-support-in-global-styles/) #### SVG Icon API Starting with WordPress 7.1, the SVG Icon API provides a standardised way to register and render custom icons in WordPress. > [Registering and rendering SVG icons in WordPress 7.1](https://make.wordpress.org/core/2026/07/24/registering-and-rendering-svg-icons-in-wordpress-7-1/) #### DataViews, DataForm, and View Config APIs The DataViews and DataForm APIs continue to mature in WordPress 7.1, alongside new View Config capabilities for controlling Site Editor screens. Developers can use the expanded APIs to customize data-driven interfaces and filterFilter Filters are one of the two types of Hooks <https://codex.wordpress.org/Plugin_API/Hooks>. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. which views and layouts are available in supported editor contexts. > [Filtering Site Editor Screens in WordPress 7.1](https://make.wordpress.org/core/2026/07/31/filtering-site-editor-screens-in-wordpress-7-1/) #### Editor WordPress 7.1 includes a broad collection of editor improvements spanning block behaviour, extensibility APIs, interface components, styling tools, and the editing environment itself. The sections below highlight the changes most likely to affect block, theme, and pluginPlugin 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. developers. ##### New Block Support WordPress 7.1 adds block support for background gradients and minimum width, allowing blocks to opt into these design controls through their metadata. The release also improves the Custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block by allowing supported blocks to remain editable inside its preview. > [New Block Support in WordPress 7.1: Background Gradient (background.gradient)](https://make.wordpress.org/core/2026/07/26/new-block-support-in-wordpress-7-1-background-gradient-background-gradient/) > [New Block Support in WordPress 7.1: Minimum Width](https://make.wordpress.org/core/2026/07/26/new-block-support-in-wordpress-7-1-minimum-width/) > [Editable blocks inside the Custom HTML block](https://make.wordpress.org/core/2026/07/23/editable-blocks-inside-the-custom-html-block/) ##### Enforced iframed editor WordPress 7.1 completes the move to an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.-based post editor, including for sites that register legacy metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes. This creates a more consistent editing environment, but plugins that rely on reaching across the editor document boundary should review their JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/) and CSSCSS Cascading Style Sheets. for compatibility. > [Iframed Editor Changes in WordPress 7.1](https://make.wordpress.org/core/2026/08/03/iframed-editor-changes-in-wordpress-7-1/) ##### Editor components The editor component library receives new features, refinements, and API updates in WordPress 7.1. Developers building editor interfaces should review the component changes for new capabilities, updated behaviour, and any migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. considerations. > [Editor components updates in WordPress 7.1](https://make.wordpress.org/core/2026/07/23/editor-components-updates-in-wordpress-7-1/) > [Miscellaneous Editor Changes in WordPress 7.1](https://make.wordpress.org/core/2026/08/04/miscellaneous-block-editor-changes-in-wordpress-7-1/) #### Design System WordPress 7.1 introduces a theming foundation for the WordPress Design System. The new approach uses design tokens and shared styles to make interfaces more consistent while giving supported environments a structured way to apply different visual themes. > [Design System Theming in WordPress 7.1](https://make.wordpress.org/core/2026/07/31/design-system-theming-in-wordpress-7-1/) #### Persistent Admin Bar The WordPress toolbar now remains available while navigating supported editor screens, creating a more consistent path between the front end, administration area, Site Editor, and Block Editor. Developers extending the toolbar should review how their items behave across these contexts and during client-side navigation. > [Consistent navigation in WordPress 7.1 with persistent toolbar](https://make.wordpress.org/core/2026/07/13/consistent-navigation-in-wordpress-7-1-with-persistent-toolbar/) #### External libraries WordPress 7.1 updates bundled third-party dependencies to improve compatibility, maintenance, and security. The most notable change is the update to jQuery UI 1.14.2, which may require testing for plugins that depend on jQuery UI behaviour or styling. > [jQuery UI updated to 1.14.2 in WordPress 7.1](https://make.wordpress.org/core/2026/07/29/jquery-ui-updated-to-1-14-2-in-wordpress-7-1/) #### Other updates Several developer-facing changes in WordPress 7.1 do not fall under any of the larger feature areas but may still affect existing integrations. These include adjustments to notification filtering and other focused API or behavioural changes. > [The notify\_post\_author filter now has the final say on post author notifications](https://make.wordpress.org/core/2026/08/05/the-notify_post_author-filter-now-has-the-final-say-on-post-author-notifications/) #### But wait, there’s more! 7.1 offers so much more! More than [180](https://core.trac.wordpress.org/query?milestone=7.1&status=closed&type=defect+(bug)&group=component&order=priority&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version) Core bugs, over [630](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Bug%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2022.7%22%20OR%20milestone%3A%22Gutenberg%2022.8%22%20OR%20milestone%3A%22Gutenberg%2022.9%22%20OR%20milestone%3A%22Gutenberg%2023.0%22%20OR%20milestone%3A%22Gutenberg%2023.1%22%20OR%20milestone%3A%22Gutenberg%2023.2%22%20OR%20milestone%3A%22Gutenberg%2023.3%22%20OR%20milestone%3A%22Gutenberg%2023.4%22%20OR%20milestone%3A%22Gutenberg%2023.5%22%20OR%20milestone%3A%22Gutenberg%2023.6%22)) Gutenberg bugs, [100](https://core.trac.wordpress.org/query?milestone=7.1&status=closed&type=enhancement&type=feature+request&group=component&order=priority&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version) enhancements and feature requests, and more than [20](https://core.trac.wordpress.org/query?milestone=7.1&status=closed&type=task+(blessed)&group=component&order=priority&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version) blessed tasks have been [marked as fixed in WordPress 7.1](https://core.trac.wordpress.org/query?milestone=7.1&resolution=fixed&group=component&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version). The following highlights call attention to smaller changes that may affect integrations, expected return values, generated markup, compatibility, or established developer workflows: **AI** – [#65504](https://core.trac.wordpress.org/ticket/65504) – AI Client – updates execute\_abilities() to mirror has\_ability\_calls() by checking is\_ability\_call() before executing, and adds regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](#blocker). 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. coverage for mixed ability and non-ability calls. **Comments** – [#65392](https://core.trac.wordpress.org/ticket/65392) – “Show more comments” fails for comment types other than comment **Editor and blocks**: * [#64838](https://core.trac.wordpress.org/ticket/64838) – Prevent block pseudo-state styles from being applied to the default state * [#65039](https://core.trac.wordpress.org/ticket/65039) – Add context to \_doing\_it\_wrong() messages in WP\_Block\_Type\_Registry::register() * [#65373](https://core.trac.wordpress.org/ticket/65373) – Query LoopLoop 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> block: add an option to exclude the current post **Formatting and compatibility** – [#42517](https://core.trac.wordpress.org/ticket/42517) – Make sure get\_file\_data() recognises headers prefixed by a <? tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). **Login, installation, and multisitemultisite 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**** – [#65506](https://core.trac.wordpress.org/ticket/65506) – Fix incorrect HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. URLs in multisite signup and activation when SSLSSL Secure Sockets Layer. Provides a secure means of sending data over the internet. Used for authenticated and private actions. is enabled **Privacy** * [#44498](https://core.trac.wordpress.org/ticket/44498) – Run \_wp\_personal\_data\_cleanup\_requests() on cron * [#44723](https://core.trac.wordpress.org/ticket/44723) – Return the WP\_User\_Request user ID as the documented type **REST API and XML** * [#65536](https://core.trac.wordpress.org/ticket/65536) – XML-RPC: fix the argument mismatch in \_multisite\_getUsersBlogs * [#65670](https://core.trac.wordpress.org/ticket/65670) – Prevent WP\_REST\_Attachments\_Controller::get\_attachment\_filesize() from failing on non-integer metadata **Themes and templates** * [#42513](https://core.trac.wordpress.org/ticket/42513) – Improve WP\_Theme::get\_post\_templates() performance for large themes * [#64848](https://core.trac.wordpress.org/ticket/64848) – Prevent implicit coercion in WP\_Theme\_JSON::to\_ruleset() * [#65049](https://core.trac.wordpress.org/ticket/65049) – Templates: add a date field #### What changes didn’t make the 7.1 release Not every feature explored during the release cycle was ultimately included in WordPress 7.1. The following initiatives were deferred, changed direction, or remained experimental, giving contributors more time to validate their design and implementation before they reach Core. > > *… as sometimes what we don’t add is more valuable than what we do*. > > > Anne McCarthy in [#7-1-release-leads](https://wordpress.slack.com/archives/C0B4Q0RJVAT/p1785803600748689) > [Roadmap to 7.1](https://make.wordpress.org/core/2026/06/19/roadmap-to-7-1/) ##### Classic block An initial proposal would have hidden the Classic block from the inserter for new content while preserving existing instances. After further discussion and testing, the change was reverted, so the Classic block remains available in WordPress 7.1. > [Hiding the Classic block from the inserter in WordPress 7.1](https://make.wordpress.org/core/2026/06/23/hiding-the-classic-block-from-the-inserter-in-wordpress-7-1/) > [The Classic block stays in the inserter for WordPress 7.1](https://make.wordpress.org/core/2026/07/07/the-classic-block-stays-in-the-inserter-for-wordpress-7-1/) The ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) 19 upgrade was also deferred beyond WordPress 7.1 and continues as an experiment in the Gutenberg plugin. > [React 19: punted beyond WordPress 7.1, experiment in Gutenberg](https://make.wordpress.org/core/2026/07/24/react-19-punted-beyond-wordpress-7-1-experiment-in-gutenberg/) ##### Real-time collaboration Real-time collaborative editing received extensive testing and feedback during the WordPress 7.1 cycle, but it is not enabled in the final release. Work continues on the editing experience, conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered *stale*, and will require a *refresh* of the changes before it can be applied, or the conflicts will need to be *resolved*. handling, compatibility, and the path toward a future Core integration. > [Announcing a collaborative editing outreach effort for 7.1](https://make.wordpress.org/core/2026/06/03/announcing-a-collaborative-editing-outreach-effort-for-7-1/) ##### “On This Day” widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. The proposed “On This Day” dashboard widget was considered during the WordPress 7.1 cycle but was not included in the release. Further work and discussion can continue in the associated TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. [#65801](https://core.trac.wordpress.org/ticket/65801). ##### Merge proposals Several projects presented merge proposals during the WordPress 7.1 cycle. Some related foundations were included in the release, while the broader proposals continue to evolve and may be considered again after further testing, documentation, and feedback. > [Merge Proposal: Guidelines built on Knowledge](https://make.wordpress.org/core/2026/06/22/merge-proposal-guidelines-built-on-knowledge/) > [Merge Proposal: Design System Theming](https://make.wordpress.org/core/2026/07/07/merge-proposal-design-system-theming/) ***Thank you to everyone who contributed to this version of WordPress, whether through code, testing, or something else – your contributions matter and help Make WordPress.*** *Props to [@joedolson](https://profiles.wordpress.org/joedolson/) and [@benjamin\_zekavica](https://profiles.wordpress.org/benjamin_zekavica/) for collaboration and review.* [#7-1](https://make.wordpress.org/core/tag/7-1/), [#field-guide](https://make.wordpress.org/core/tag/field-guide/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F08%2F05%2Fwordpress-7-1-field-guide%2F%23respond&locale=en_US "Login to Reply"), WordPress 7.1 Field Guide, Milana Cap, 01kz978fa2135vhbtaetjr4984.