WordPress 7.2 has been available as a Release Candidate since November 17, and the final version is planned for December 8, 2026. The Field Guide for developers from November 20 lists more than 440 changes to the WordPress core, including almost 150 enhancements and over 260 bug fixes.
For site owners, four changes matter: new icons in the admin menu, an email when new application passwords (separate access codes for apps) are created, a different debug default for local environments, and an SQL mode that WordPress turns off itself. Image processing in the browser is covered in the TutKit news from November 21.
What changes in the admin area?
WordPress replaces the icons of the Dashicons font in the admin menu and in the admin bar with embedded SVG icons. Most plugins and themes continue to work unchanged. Customized color schemes, custom icons, and CSS that targets pseudo-elements of the Dashicons may need adjustment.
According to the further developer notes, the greeting "Howdy" moves from the bar into the user menu, and only the display name and avatar remain at the top. The menu item for adding themes returns to the Appearance menu. In addition, every user receives an email as soon as an application password is created for their account, whether via the profile, the access authorization page, or the REST API.
Sites that already notify users about new application passwords themselves can turn off one of the two notifications: the filter wp_send_application_password_created_email returns false.
What changes behind the scenes?
On sites with the environment type local, a local development environment, WordPress 7.2 will in future turn on debug output automatically, provided the wp-config.php does not define WP_DEBUG. Warnings and notices about deprecated functions then appear in the browser. With WP_DEBUG_DISPLAY set to false and WP_DEBUG_LOG set to true, they end up in the log file. On staging and live sites, debug output stays off. A setting in the wp-config.php still takes precedence.
In addition, WordPress turns off the SQL mode NO_BACKSLASH_ESCAPES for its database connection. WordPress assumes backslashes are used to escape special characters; the mode makes queries fail, especially with hosts that enable it by default. The change applies only to the WordPress session; the server's setting remains untouched.
For developers, the Field Guide names two plans. WordPress 7.2 updates jQuery Migrate to version 3.6.0; 7.2 does not yet ship jQuery 4 itself. According to the plan, the update to jQuery 4 is provisionally scheduled for 7.3. With 7.4, eight deprecated components of the editor library @wordpress/components are to be removed, including Animate, Divider, and ZStack.
When is 7.2 coming, and what else is new?
The announcement of the Release Candidate mentions, among other things, a new default theme called Ipsum. According to the Field Guide, text shadows are coming for the "Paragraph" and "Heading" blocks, with the presets "Light" (slight) and "Strong" (heavy). The new address /random/ redirects visitors to a randomly selected published post; the filter wp_enable_random_content_redirect turns it off.
WordPress 7.2 schedule
Dates according to WordPress.org and Make WordPress Core
- November 17, 2026Release Candidate 1 is ready for testing
- November 20, 2026Field Guide for developers is published
- December 8, 2026Planned release of WordPress 7.2
- AnnouncedUpdate to jQuery 4, provisionally scheduled for 7.3
December 8 is a planned date and may shift.
Sources: Make WordPress Core, WordPress News
WordPress warns against testing the Release Candidate on live sites. It can be installed on a test server via the Beta Tester plugin, as a ZIP file, or with WP-CLI; without installation, it runs in WordPress Playground, a test environment in the browser.
What this means for you
Before December 8, make a copy of your site and install the Release Candidate there, most easily in WordPress Playground. Then open the admin area and check whether your custom color schemes and icons are still correct. Also test all plugins that modify the admin menu.
With the environment type local and without your own WP_DEBUG line, you will suddenly see warnings in the browser after the update. It is best to define the line yourself. Tell users with application passwords in advance so that the new email does not confuse anyone.
As a developer of plug-ins or themes, you test your JavaScript with jQuery Migrate 3.6.0 and replace the deprecated components by 7.4. The WordPress team published the Field Guide on November 20, 2026.
Sources