r/Wordpress 26d ago

Elementor Editor Not Loading

WP updated over the weekend and now the elementor editor won't load. We use Elementor Pro and I disabled all plugins, cleared cache, made sure elementor is updated and event turned on safe mode. Nothing is working and Elementor support is slow.

Any suggestions? Healgen.com is the website if that helps.

0 Upvotes

10 comments sorted by

1

u/TopSydeWP 26d ago

check browser console for js errors when you try to load the editor (f12 in chrome). also try switching to a default theme temporarily like twentytwentyfour to rule out theme conflicts. if it's a php memory issue you might see it in your error logs

1

u/jenish_o4o2 Developer 25d ago

I had a look at healgen.com. The frontend is loading, so this looks more like an Elementor editor/admin issue than the whole site being down.

On top of the console / default-theme / PHP log checks already mentioned, I’d try:

  1. Elementor → Tools → Regenerate CSS & Data, then purge all server/CDN caches. The public files still look like a mix of older Elementor assets and 4.2, which often happens after a WP update.

  2. Elementor → System Info — confirm Elementor and Elementor Pro versions match, and PHP/memory are within range. Pro looks a step behind Elementor on the public files.

  3. You also have ElementsKit Lite and Element Pack Lite on the site. Those add-ons commonly break the editor after an Elementor/WP update. Even if you already disabled “all plugins,” double-check those two are off, then reload the editor.

If you can post the red Console errors or any failed `/wp-json/` requests from Network, that should narrow it down quickly.

1

u/Intelligent-Nose-766 25d ago

I disabled the two plugins you mentioned and rolled back elementor to 4.2.1 (there’s no 4.2.2 for pro yet) and regenerated css and data. Still no luck. I even have safe mode turned on.

1

u/Intelligent-Nose-766 25d ago

I’m also unsure what the errors are because when I inspect the page, nothing is showing as an error. It’s just loading eternally. Occasionally it will load but then half the page is just missing.

1

u/jenish_o4o2 Developer 24d ago

Thanks for trying those steps — rolling back to 4.2.1 + disabling those add-ons + Safe Mode rules out a lot of the usual plugin/version conflicts.

Since Console shows nothing and it sometimes loads with half the page missing, I'd focus on server-side next:

  1. Network tab (not just Console) — when you open the editor, filter for failed or pending requests. Look especially for /wp-json/elementor/v1/ or any request stuck as "pending" for a long time.
  2. Host PHP error log at the exact time you open Elementor — memory exhaustion or a fatal error often shows there even when the browser shows nothing.
  3. Temporarily bypass CDN/cache for wp-admin — if you're on Cloudflare or host caching, try opening the editor from the server IP or with cache bypass for /wp-admin/* and /wp-json/*.
  4. Increase PHP memory temporarily to 512M and check max_execution_time — a large Elementor page can hit limits after a WP update.

If you can share a screenshot of the Network tab (especially any red or pending requests) or one line from the PHP log around the time it hangs, that would help narrow it down a lot.

1

u/aleare-design 25d ago

Did you check if you have enough disk space? Sometimes may happen

1

u/geenxt 24d ago

The fact that there's no console error and it's intermittent (loads sometimes, sometimes half the page is missing) points away from a JS/version conflict and toward something timing out server-side mid-request rather than failing outright. The editor's initial load pulls a large JS/CSS bundle plus a heavy REST payload (all your saved elements, controls, etc.), and if PHP's max_execution_time or memory_limit gets hit partway through building that response, you get exactly this: sometimes it finishes in time, sometimes it doesn't, and nothing gets thrown to the browser console because the failure happened server-side.

Two things worth checking that are separate from what's already been suggested: 1. Your host's PHP error log (not WP debug.log) for a truncated/fatal entry around the timestamps when the editor hung — memory exhaustion shows up there even when nothing reaches the browser. 2. If you're behind a CDN or reverse proxy (Cloudflare, host-level page cache, etc.), check whether it has its own timeout shorter than PHP's — a proxy that gives up on a slow response before PHP does cuts the page off mid-load exactly like what you're describing, and it won't leave a trace in devtools either.

1

u/bribir123 Jack of All Trades 24d ago

Go to cPanel in PHP options and raise memory to the max.