The block editor is itself a fairly heavy JavaScript application layered on top of the classic post-editing screen, and if any single script it depends on fails to load — a plugin conflict, a PHP error during the page’s setup, an incompatible browser extension — the whole editor can fail to initialize, leaving you staring at a blank or perpetually-spinning edit screen with no obvious error. Because the failure happens before the editor’s own interface has rendered, WordPress has no mechanism at that point to show you a helpful message — the screen simply never finishes loading.
Before you buy, one quick check
Read-only. Open the affected post’s edit screen, then open your browser’s developer console (F12, or right-click and choose Inspect, then the Console tab) and look for a red error message.
A specific JavaScript error naming a plugin or script file is a strong clue about the cause, and it’s useful information to have ready even if you don’t recognise what it means yourself.
Try the same post in a different browser too, since a result that changes between browsers points toward an extension or browser-specific quirk rather than a genuine site-wide fault.
It’s also worth noting exactly when the problem started, since a failure that began right after installing or updating a specific plugin is a much stronger lead than one that seems to have appeared on its own.
Block editor not loading - diagnosis
The block editor won't load, or the screen just spins. We find the script conflict or PHP error causing it and get the editor working again.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Block editor screen loads blank, spins indefinitely, or throws a visible error | This fix covers it |
| Editor loads but a specific block type is missing or broken | A narrower, block-specific fix |
| Classic editor works fine, only the block editor fails | This fix covers it |
| The issue is content converted from Classic looking wrong once opened in blocks | Classic-to-block content conversion |
| The whole admin area is inaccessible, not just the editor | A broader site-down diagnosis |
What you are seeing
- The block editor screen loading blank or stuck on a spinner indefinitely
- A visible error message where the editor should load
- The problem affecting all posts and pages, or only specific ones
- The classic editor, if available, still working normally
- A browser console error referencing a specific script or plugin
Common causes
- A plugin enqueuing a script that conflicts with or blocks the block editor’s own scripts
- A PHP error during page setup that prevents the editor’s JavaScript from ever loading
- A browser extension interfering with the editor’s interface
- Corrupted block content in a specific post causing the editor to fail parsing it
- An outdated or incompatible plugin still hooking into editor functions removed in newer WordPress versions
What we do
- Reproduce the failure and capture the specific console error or PHP log entry
- Determine whether the cause is site-wide or isolated to specific content
- Identify the conflicting plugin, script, or corrupted block markup responsible
- Resolve the conflict or repair the affected content
- Confirm the block editor loads and functions normally across affected posts
- Check that saving, previewing, and publishing all work correctly afterward
What is included
- The specific cause of the block editor failing to load identified and resolved
- Testing across the affected posts or pages to confirm recovery
- A check that publishing and previewing work normally afterward
- The pre-fix backup, kept for 30 days
Not included
- Converting content between classic and block formats, which is a separate service
- Fixing bugs in a specific third-party block plugin’s own code
- Rebuilding content that was already corrupted before this fix was ordered, beyond making it loadable
- Ongoing monitoring for future plugin conflicts
Questions about this fix
Will I lose the content in the post that won't open?
We aim to recover it as-is; if the underlying block markup is genuinely corrupted, we'll tell you plainly what's recoverable before doing anything to the post.
Does this mean I have to stop using the block editor?
No — the goal is to get the block editor working properly again, not to steer you toward the classic editor instead.
Could a browser extension really cause this?
Yes, ad blockers and certain privacy extensions occasionally interfere with editor scripts, which is why checking in a different browser or incognito window is sometimes a useful clue, though not always conclusive.
Is this the same as the block editor being slow, rather than not loading at all?
No — a slow editor is a performance issue with a different cause; this fix is for the editor failing to load or initialize at all.
Why does this only affect some posts and not others?
Usually because those specific posts contain a block or piece of content the editor is failing to parse, rather than the editor itself being broken site-wide.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.