6.9 shipped with a set of admin bugs that should have been caught before release, and WordPress 6.9.1 RC1 is the cleanup. If you have been dealing with broken checkboxes in the admin or mail that sometimes just does not send since you upgraded, this is the release candidate to grab.
There are no new features in WordPress 6.9.1 RC1. It closes 23 core bugs and 25 Block Editor issues, which is what a maintenance release is for. On a busy WooCommerce store or a multisite install, this is the category of bug that generates the support tickets nobody budgeted for.
What WordPress 6.9.1 RC1 actually fixes
The HTML API was double-escaping class names. If you build custom blocks or use the HTML API to rewrite tags, that is where your duplicated or mangled classes were coming from. The wp_mail_succeeded filter had a gap too: the $embeds element was missing from it, which is enough to break a transactional email workflow that depends on that filter.
Then there is the Could not instantiate mail function error. Fourteen years into debugging WordPress, mail is still the failure I least enjoy explaining to a client, because it is almost never the server. Usually it is a dependency conflict or a transient that got written wrong. This RC fixes that regression, and it fixes the broken styling on the “Add Plugins” screen that left the dashboard looking half-loaded.
If you are still on 6.9 and patching around this, my earlier notes on dealing with WordPress 6.9 hotfixes cover what we did before the RC landed.
How to test the RC without breaking production
Test it on staging with WP-CLI instead of on the live site. It is the quickest way to find out whether your plugin stack survives the update. Pull the build with:
# Update to the latest WordPress 6.9.1 RC1 build via WP-CLI
wp core update https://wordpress.org/wordpress-6.9.1-RC1.zipKeep an eye on your XDebug configuration too. Ticket #63979 covers core setup not configuring XDebug correctly, which quietly wrecks local performance. If your local environment has felt sluggish, that one fix may be reason enough to update.
WordPress 6.9.1 RC1 also warns you when you enqueue a script or module with a missing dependency. That used to fail silently, and you found out about it from the browser console an hour later.
Gutenberg fixes, starting with an infinite loop
On the Block Editor side, PR #73955 fixes an infinite loop in the Font Style UI inside Global Styles. Loops like that can take a browser tab down and leak a lot of memory on the way. The final release is set for February 3, 2026, so there is a short window to run the RC against your own setup first. The 6.9.1 release schedule has the rest of the dates.
If chasing WordPress 6.9.1 RC1 regressions is eating your week, I can take it off your plate. I have been working with WordPress since the 4.x days.
What to do before February 3
Most of the attention right now is on WordPress 7.0, but 6.9.1 is the release that keeps the sites you already run working. Test your mail paths and check your block attributes on staging before the final ships. If something is still broken, report it in the #6-9-release-leads Slack channel while there is time to fix it.
