Symptoms
- The editor remains on a loading screen or its panel is blank.
- Saving returns a 403, 500, JSON, or REST API error.
- The editor works for one page, browser, or administrator but not another.
Likely causes
Potential causes include a JavaScript error, extension conflict, cache, blocked REST request, insufficient PHP memory, outdated components, malformed content, security rule, or server error. A loading spinner is a symptom, not a diagnosis.
Diagnostic steps
- Create a backup or staging copy and record recent changes.
- Check browser console and network requests for the first meaningful error.
- Confirm Site Health, REST API, loopback requests, PHP limits, and server logs.
- Test a private browser window and clear only relevant caches.
- Use Elementor Safe Mode when available, then perform a controlled theme/plugin conflict test on staging.
- Compare a new blank page with the affected page and avoid editing serialized content directly.
Resolution steps
Update compatible components, correct the failing request or server limit, remove the proven conflict, regenerate Elementor CSS/data through supported tools, or restore the affected content from a known-good revision. Re-enable components one at a time.
Escalation conditions
Escalate with WordPress, Elementor, PHP, and browser versions; sanitized console and server errors; reproduction steps; the conflict-test result; and whether a new page is affected. Never send administrator passwords in a ticket.
Customer-safe explanation
“The editor is waiting on a request that is not completing normally. We are identifying that first failed request and testing safely on staging so the live page is not put at risk.”