If an Elementor update broke your WordPress site, don't start rebuilding pages. Roll Elementor and Elementor Pro back to the last version that worked from Elementor > Tools > Version Control, run Regenerate Files & Data and purge every cache. If WordPress shows a critical error and you can't log in, disable the plugin over SFTP first, then roll back. Once the site is stable, find the real cause on a staging copy before you update again.
That's the short version. The rest of this post is the plan I'd follow on a live business site, and it has two parts: get the site back today, then stop the next update doing the same thing. I've worked with Elementor for 4+ years, on builds like Crowne Plaza London Kingston, the Warren House homepage, Samko Holdings and the Cyprianis revamp. This is the order I work in.
What usually breaks after an Elementor update?
Most Elementor update problems fit one of five patterns: a critical error, unstyled pages, a stuck editor, missing widgets or broken Elementor Pro features. Match your symptom before you touch anything. Each one has a different fix, and guessing wastes time.
| Symptom | Likely cause | First thing to try |
|---|---|---|
| "There has been a critical error" or a white screen | A PHP fatal error, often because Elementor and Elementor Pro are on mismatched versions, or because an add-on calls code that changed | The recovery mode link, or disable the plugin over SFTP |
| Pages look unstyled or the spacing is wrong | Old CSS files, or a cache still serving the previous version's styles | Regenerate Files & Data, then purge all caches |
| Editor stuck on the loading spinner | A conflict with another plugin or the theme, or low PHP memory | Safe Mode |
| Widgets missing or blank | A third-party add-on pack that doesn't support the new Elementor version yet | Update or disable the add-on |
| Popups, forms or theme templates stop working | Elementor Pro wasn't updated with core, often because the licence expired | Update or roll back both plugins together |
Elementor update broke my site: what do I do first?
Back up the broken site, get into wp-admin, roll back Elementor and Elementor Pro, then regenerate CSS and purge caches. Go through these in order and stop as soon as the site is back. Finding the cause comes after.
- 1
Back up the broken state
Take a full backup of files and database before you change anything, so you can always get back to where you started.
- 2
Get back into wp-admin
Use the WordPress recovery mode email, or rename the plugin folder over SFTP if you're locked out.
- 3
Roll back Elementor and Pro
Go to Elementor > Tools > Version Control and return to the last version that worked, keeping core and Pro on matching versions.
- 4
Regenerate CSS and purge caches
Run Regenerate Files & Data, then clear your caching plugin, server cache, CDN and browser.
- 5
Find the conflict
Use Elementor Safe Mode and the error log to find which plugin, theme or setting is causing the clash.
Backing up a broken site sounds odd. Do it anyway. If a fix goes wrong, you want to land back on "broken but known", not somewhere worse.
What if I can't log in at all?
Since WordPress 5.2, a fatal error triggers recovery mode. WordPress emails the admin address a login link that pauses the broken plugin for your session only. Look for that email first, and check spam.
If it never turned up, connect over SFTP or your host's file manager, open wp-content/plugins/ and rename elementor-pro to elementor-pro-off. Reload the site. Still down? Do the same with elementor. WordPress deactivates any plugin it can't find, and your page content stays in the database. Pages will look bare without Elementor, but you'll be back in wp-admin, which is all you need at this stage.
How do I roll back Elementor and Elementor Pro?
Elementor has a built-in rollback under Elementor > Tools > Version Control. Pick the version you ran before the update. If you use Elementor Pro, roll that back as well, to a release from the same period. Mismatched core and Pro versions are a frequent cause of breakage, so treat the two plugins as one unit, always.
If the dashboard won't load far enough to reach that screen, the free WP Rollback plugin can reinstall an older version of free Elementor from WordPress.org. Elementor Pro isn't on WordPress.org, so roll it back from Version Control once you're in.
Don't get comfortable on the old version. A rollback buys you time to find the real problem, nothing more. Old Elementor versions miss security patches, so plan to update again within days, on staging.
How do I regenerate CSS and clear every cache?
Elementor writes each page's styles to CSS files, and after an update those files can be out of date. Go to Elementor > Tools, click Regenerate Files & Data, then Sync Library.
Then purge every cache layer:
- your caching plugin
- any server cache your host runs
- Cloudflare or any other CDN
- your own browser, with a hard refresh
A layout that looks broken is often a CDN still serving old CSS.
If styles still don't load, check the CSS print method in Elementor's settings. Switching from external files to internal embedding is a quick test of whether file permissions or caching are to blame.
How do I use Safe Mode to find plugin conflicts?
If the Elementor editor won't load, turn on Safe Mode under Elementor > Tools. It runs the editor with only Elementor active and a default theme. It only affects the editor, so visitors see the normal site. If the editor works in Safe Mode, something else on the site is clashing with the new Elementor version.
To find out what, copy the site to staging and deactivate plugins one at a time. Or use the Health Check & Troubleshooting plugin, which disables plugins for your session only. Common culprits are:
- Elementor add-on packs
- optimisation plugins that minify, combine or delay JavaScript
- outdated themes
While you're in the dashboard, open Elementor > System Info and write down your PHP version, memory limit and the exact Elementor and Elementor Pro versions. Any developer you bring in will ask for these first.
How do I read the error log?
For critical errors, turn on logging in wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Errors go to wp-content/debug.log, and visitors won't see them on the page. The fatal error line names the file and plugin at fault. Paste it into my free Error Message Explainer for a plain-English explanation and the likely fix. If your host upgraded PHP around the same time, read how to fix a critical error after a PHP upgrade too. The debug.log file is publicly accessible by default, so once you've found the error, delete the file and set WP_DEBUG back to false.
Should I roll back, update forward or restore a backup?
Roll back Elementor if the site is down and has to work today. Restore a full backup only if several plugins updated at once and you can't pin down which one did it. The permanent fix is either updating the add-ons and theme, or fixing the custom code the update broke.
| Option | When it makes sense | Watch out for |
|---|---|---|
| Roll back the plugin | The site is down and you need it working today | You miss security fixes until you update again |
| Update add-ons and theme | The add-on or theme has released a version that supports the new Elementor | Test on staging first, because the new version may bring its own problems |
| Restore a full backup | Several plugins updated at once and you can't isolate the problem | You lose any orders, bookings and form entries made since the backup |
| Fix the code | Custom code or a child theme uses functions the update changed | Needs a developer, but it's the only permanent fix |
One catch with rolling back: some major Elementor releases run a database update after install, and rolling back the plugin doesn't reverse it. So a backup taken before the update is worth more than the rollback button. If you don't have one, that's the first thing to fix once the site is up.
Why do some Elementor sites break and others don't?
Elementor sites break on update when they have lots of moving parts and no update routine. Every Pro popup, form, theme builder template and third-party widget is one more thing an update can knock over.
The Elementor sites I've built vary a lot here. Crowne Plaza London Kingston has rooms linked to IHG booking, meeting forms and promo popups. Warren House has a video hero and Google reviews. Cyprianis has an events listing and a private dining template built from Figma. Samko Holdings runs on Elementor Pro. More features means more to check after each update.
The sites that break on update tend to have a few things in common:
- Auto-updates are on for Elementor, so changes land with nobody watching.
- The Elementor Pro licence has expired, so core keeps updating while Pro falls behind.
- Several add-on packs are installed, each on its own release schedule.
- Custom code in a child theme hooks into Elementor internals.
- There's no staging site, so the first test happens in front of live customers.
I don't think any of this means Elementor is the wrong tool. It means the site needs an update routine. And if it's slow as well, speeding up an Elementor site often removes the same add-ons that cause the conflicts, so you fix two problems at once.
How do I stop Elementor updates breaking my site again?
Back up offsite, test every update on a staging site first, update Elementor and Elementor Pro together and turn off auto-updates. Then check the same key pages after every update, every time.
Test every update on staging first
Clone the live site to staging, run the Elementor and Elementor Pro updates there and check your key pages before touching live. A broken staging site costs you nothing. A broken live site costs you enquiries.
The routine I recommend:
- Back up files and the database to offsite storage, with a tool like UpdraftPlus or your host's snapshots. Keep several restore points, not just the latest.
- Clone the site to staging with your host's one-click staging or a plugin like WP Staging.
- Update everything in one go: Elementor, Elementor Pro and any add-ons in the same session.
- Check the same pages every time: the homepage, header and footer, a popup, every form, booking or checkout, and the mobile view.
- Regenerate files, then repeat the update on live at a quiet time of day.
- Watch it for a day: form submissions, analytics and the error log.
On top of that, turn off auto-updates for Elementor and Elementor Pro, keep the Pro licence active and delete add-ons you no longer use. Fewer plugins, fewer surprises.
When is a maintenance retainer worth it?
A WordPress maintenance retainer is worth it when your site takes bookings, orders or enquiries and nobody on your team has time to test updates on staging. Downtime costs you money. The routine above is the first thing that gets skipped in a busy week.
That's the gap a retainer fills. Someone runs updates on staging, keeps backups, watches uptime and fixes problems before customers notice. I run a monthly retainer for IPL Biologicals covering new pages, catalogue updates and store support, and the same update routine applies to Elementor sites. For the full list, see what a WordPress maintenance retainer covers.
What should I ask a developer before they touch it?
Ask how they'll protect the site while they fix it. You want backups first, fixes on staging, the cause written down and your access kept. These five questions cover it:
- Will you back up the broken site before changing anything?
- Will you test fixes on staging, not live?
- What caused it, and will you write that down for me?
- Which Elementor and Elementor Pro versions will you leave me on, and when should I update next?
- Will I keep admin, hosting and DNS access when you're done?
I'd pick a developer who answers these clearly over one who promises the fastest fix.
What should I do next?
If your Elementor site is down right now, send me a message with:
- the site URL
- what you updated
- the Elementor and Elementor Pro versions from System Info
- any error message you're seeing
I'll tell you whether it's a quick rollback or something deeper. If the site's back up and you want this to be the last time, ask me about a maintenance retainer. And if the site has outgrown its patchwork of add-ons, I also build and rebuild WordPress sites on Elementor and Bricks.
