WordPress 7.1.4 broke my editor? What's known and what to try

01

What 7.1.4 changed

The release post calls it a security release with "fixes for multiple issues" and recommends updating immediately. The HelpHub page for 7.1.4 lists the fixes. Almost all are cross site scripting or permission issues, plus a race condition in the core update process and an update to bundled root certificates. Our 7.1.4 security release post goes through them.

Neither page mentions an editor change or a known editor bug. As of 1 November, the support threads below don't point at a 7.1.4 core bug either. So treat "7.1.4 broke it" as a lead you still need to test.

02

What owners are reporting

These are real threads from the last week of October, with what each one turned out to be so far.

Missing file names after upload

One owner wrote "since the 7.1.4 update, I've noticed that after uploading media, the file name isn't saved". A moderator couldn't reproduce it on a clean install. The owner later marked it resolved: a plugin had registered the update_attached_file filter as an action.

Blank editor on the 7.1 branch

In this thread, the browser console showed Promise.withResolvers is not a function. A forum moderator explained that core uses that browser feature from WordPress 7.1, and that it needs Chrome or Edge 119, Firefox 121 or Safari 17.4 or later. The owner was on Firefox 115 and chose to stay on 7.0.

"The editor has crashed."

The error report in this thread is r.toSorted is not a function, and every file in the stack trace sits under wp-content/plugins/gutenberg/. That points at the Gutenberg plugin and the browser, so test those before blaming core. It's still unresolved.

Every admin screen redirects to Profile

This owner saw it start around 29 October on two sites at the same host. Replies suggested the shared Redis object cache or a host plugin in mu-plugins, since both sites broke together.

Plugins and Settings menus gone

On X, an owner posted on 28 October: "after updating my plugins my plugins tabs disappeared so did the settings tab in WordPress I'm on 7.1.4". Note the first words. Plugins were updated at the same time, and when menus vanish for an administrator, a role or capability change is the first thing to check.

"Updating failed. Could not get a valid response from the server."

In this thread the reply was that the editor can't reach the REST API. Check Tools > Site Health for a REST API error, and ask your host whether a firewall blocks /wp-json/.

03

Step 1: open the browser console

The block editor runs in your browser, so its errors show up there. Open the broken screen, press F12, pick the Console tab and reload. Copy any red error. If it says something "is not a function", update your browser first and test again.

04

Step 2: rule out plugins and the theme

Deactivate all plugins, switch to a default theme, and test in a private window to rule out browser extensions. If you can't reach the Plugins screen, rename wp-content/plugins over FTP, or use WP-CLI:

wp plugin deactivate --all

Then turn plugins back on one at a time. The Gutenberg plugin deserves its own test, since it replaces the editor that ships with core.

05

Step 3: check the server side

A blank screen with no console error usually means PHP failed. Turn on WP_DEBUG_LOG as described in Debugging in WordPress and read wp-content/debug.log. Also look in wp-content/mu-plugins/ and ask your host if anything on their side changed recently, such as caching.

06

Step 4: roll back only if you must

The 7.1.4 fixes were backported to older branches, so a rollback within the same branch line keeps you patched. Per the release notes, only the most recent version is actively supported. If you need to drop back to 7.0, use the latest 7.0 release, which is 7.0.8 in the releases archive as of 1 November. With WP-CLI:

wp core update --version=7.0.8 --force

Take a full backup first, files and database. Going back to 7.1.3 removes the security fixes, so don't do that.

07

Step 5: report it

If a clean install with no plugins and a current browser still breaks, you may have found a real bug. The core bug reporting handbook explains how to search for an existing report and file a new one. Include your WordPress version, browser version, the exact console error and the steps to reproduce.

08

Sources

• WordPress 7.1.4 release post
• Version 7.1.4 (HelpHub)
• "Media upload, missing filename"
• "Editor page BLANK since branch 7.1"
• "The editor has crashed. An unknown error occurred."
• "After 7.1.4 auto-update, every wp-admin screen redirects to profile.php"
• "Updating failed. Could not get a valid response from the server."
• X post, 28 October 2026
• Debugging in WordPress
• Reporting bugs (Core handbook)
• WordPress releases archive