Why won't my page editor load, or my changes save?

Suggestions appear as you type. Use the up and down arrows to choose one, or press Enter to ask.

If the editor won't open, spins forever or says "Updating failed", the cause is usually a plugin clash after an update, the server running out of memory, or a security rule blocking the save. If you can't see any edit tools at all, your login may not have editing rights. Copy your text somewhere safe, then report the exact message.

Why can’t I see any edit tools?

  1. Check you’re logged in. Go to your site’s login page and sign in again. See logging in to your website.
  2. Check it’s the right site. Staging copies, old sites and your live site can look alike. Look at the address bar.
  3. Check your role. WordPress roles decide what you can change. A Subscriber can only manage their own profile. Authors and Contributors work on posts, not pages. Editing pages needs Editor or Administrator.
  4. Ask an administrator to change your role if you need more. See adding or changing someone’s access.
    • Expected result: the toolbar at the top shows Edit Page, and your page builder’s launch button if your site uses one.

The short version

  • Save your work first. Copy your text into a document before trying anything else.
  • Try once in a private window. Still failing? Stop and report it. Don’t turn plugins off on a live site.

Why won’t the editor load or save?

  1. Read the message. Note the exact words: “Updating failed”, “Publishing failed”, “The response is not a valid JSON response”, or a spinner that never stops.
  2. Try a private or incognito window, or clear your browser’s cache using Google’s steps for Chrome. WordPress’s own troubleshooting FAQ lists the browser cache as a common cause when Publish or Save Draft does nothing.
  3. Try a different browser. Browser extensions, such as ad blockers, can stop an editor from loading.
  4. Save smaller changes. A very long page, or text pasted from Word, can be slow to save. Paste as plain text and save often.

If none of that works, the problem is almost always on the server: two plugins clashing after an update, the site running out of memory, or a security rule that mistakes your save for an attack. WordPress’s common errors guide covers the memory error. All three need someone with server access.

Why does this matter?

When an editor breaks right after an update, the safest fix is found on a copy of the site, not the live one. Testing plugins one by one on a live business site can take down pages customers are using.

What are the common mistakes and edge cases?

  • Losing a long edit. If the save fails, don’t close the tab until your text is copied somewhere safe.
  • Shared logins. If several people use one login, someone may have changed its role or password. Give each person their own.
  • It works on one computer only. That points to the browser or an office network rule. See why a change isn’t showing.
  • Uploads fail but text saves. That’s a separate problem. See why I can’t upload images or files.

What if this didn’t work?

Send your web team the page address, the exact message, your browser, and roughly when it started, plus anything that changed recently. Never send your password. If you need the change made today, send the text and we can make it for you.

How does E-3 handle this?

For a site E-3 looks after, call 814-399-4655 or email support@e3help.me. A person at E-3 reads the server and error logs, finds the plugin clash, memory limit or security rule behind it, and tests the fix on a staging copy before it goes on your live site. If your role is the problem, we confirm who’s asking before changing anyone’s access. Replies usually come within one business day.

Did this fix it?

Rather talk it through?

Call our team, or send a note and we’ll reply within one business day. No pressure and no jargon.

Ask E-3

Suggestions appear as you type. Use the up and down arrows to choose one, or press Enter to ask.

Get support