The WordPress 7.2 Field Guide, published Friday, November 20, gathers the release’s developer changes in one place as WordPress moves through its Release Candidate phase. It covers API updates, editor changes, compatibility notes, and several specific checks for plugin and theme developers.
If you maintain WordPress extensions or custom site code, the guide gives you a practical starting point for reviewing what could need attention before upgrading. Its most immediate checks concern media uploads, editor components, bundled JavaScript packages, and API input handling.
Quick answer: Review the WordPress 7.2 Field Guide against the code your plugin or theme uses. Test browser-based media processing and admin interfaces, update affected bundled packages, and check any integrations with the Abilities API, Interactivity API, and REST API. The guide describes changes in the 7.2 release candidate, not a final release.
What the WordPress 7.2 Field Guide covers
The guide tallies more than 440 Core Trac tickets in WordPress 7.2, including almost 150 enhancements and feature requests and more than 260 bug fixes. It also lists 40 tickets focused on the Editor. Accessibility received 48 tickets, tests 34, and performance 26.
Gutenberg versions 23.7 through 24.3 add almost 700 enhancements and nearly 500 bug fixes, according to the guide. A comparison between WordPress 7.1.4 and the 7.2 release candidate also identifies 21 new hooks: 16 filters and five actions.
Those counts show the breadth of the release, but the compatibility notes are more useful for a developer planning an upgrade. The field guide groups changes by area and links to the individual developer notes for further detail.
Media processing moves into more upload screens
WordPress 7.2 extends client-side media processing, introduced in 7.1, to the Media Library grid, the Add New Media File screen, and the media modal. Supported resizing, format conversion, and image sub-size generation can happen in the browser rather than on the server.
This behavior depends on browser and device support. The guide says the feature works in Chromium-based browsers such as Chrome 137 and later and Edge 137 and later. Firefox and Safari fall back to server-side processing because they do not support the required Document-Isolation-Policy. Even supported browsers need more than 2 GB of device memory and compatible processing and security settings.
Developers who customize upload flows should check how their code detects media uploads. The new pipeline uses REST API requests rather than async-upload.php, and some request details differ. The field guide’s media section explains which upload hooks still run and which request checks may miss the new path.
Editor and block changes need targeted checks
WordPress 7.2 adds text-shadow support for Paragraph and Heading blocks, with presets that themes can define in theme.json. Custom blocks can opt in through supports.typography.textShadow. The Options and View menus also switch to the Menu component from @wordpress/ui, with updated keyboard navigation and accessibility semantics.
There is a more direct migration task for extensions that bundle editor packages. The release changes CSS module class generation to reduce collisions when different versions of the same package appear on a page. The guide names minimum versions for @wordpress/ui, @wordpress/dataviews, @wordpress/admin-ui, @wordpress/grid, and @wordpress/components. Plugins using @wordpress/build to compile CSS modules should update to version 0.27.0 or later and rebuild their assets.
Some editor components are also deprecated, with removal scheduled for WordPress 7.4. The listed components include Animate, Divider, Elevation, ResponsiveWrapper, Scrollable, Surface, Tip, and ZStack. Developers using them should review the guide’s alternatives rather than waiting for the removal.
API updates affect permissions and content handling
The Abilities API now supports a required_capabilities registration argument, and input preparation is standardized through WP_Ability::prepare_input(). The guide advises developers to check permission callbacks, input assumptions, and JSON response handling. Empty values declared as JSON objects are now preserved as objects rather than serialized as arrays.
The Interactivity API adds the data-wp-html directive and new client-side navigation state. Its HTML-rendering functions do not sanitize content, so code using them must supply trusted, properly sanitized HTML. The release also removes previously deprecated directive behaviors, including data-wp-ignore.
REST API changes touch revision metadata, comment status parameters, and CORS headers. Revision and autosave responses now include only metadata registered for revisions. The comments endpoint treats status as an array, and a new filter lets developers customize the allowed CORS methods header.
Other checks for plugin and theme teams
The administration menu and toolbar replace Core Dashicons font glyphs with inline SVG icons. Most existing plugins and themes are expected to continue working without modification, but custom admin color schemes, icon replacements, and CSS selectors targeting Dashicons pseudo-elements may need changes.
WordPress 7.2 also updates jQuery Migrate to version 3.6.0 to help developers find deprecated JavaScript behavior ahead of a future jQuery 4 transition. The guide says 7.2 does not include jQuery 4. It also introduces a /random/ endpoint for redirecting visitors to published content, and changes how WordPress handles the NO_BACKSLASH_ESCAPES SQL mode within its database session.
For a first pass, search your codebase for the deprecated editor components and API behaviors named in the guide, then test media uploads and admin screens in a 7.2 test environment. Add checks for any package versions you bundle yourself. These are concrete places to start, not a claim that every site or extension will need code changes.
WordPress 7.2 Field Guide FAQ
Is WordPress 7.2 final?
No. The field guide was published during the Release Candidate phase and describes the 7.2 release candidate. Treat its notes as preparation for the release, not as confirmation that the final version is available.
Which developers should read the guide?
Plugin and theme developers should check the compatibility notes, especially if they bundle WordPress JavaScript packages or customize media uploads, editor components, admin icons, or API behavior. Developers maintaining custom integrations can use the API sections to identify affected code paths.
What should I test first?
Start with the parts of your code that touch media upload requests, editor package styles, deprecated components, and API permissions or input. Then test the relevant workflows with the 7.2 release candidate in a non-production environment.
Next step: compare your plugin or theme’s dependencies and customizations with the field guide, then file specific compatibility issues while the release is still in candidate testing.