THE SHORT ANSWER
The error "Depending on a hidden experiment is not allowed" is a fatal error thrown when Elementor 4.3.0 or 4.3.1 runs next to an older Elementor Pro release. Pro's mega menu module depends on the nested-elements experiment, which 4.3.0 marked as hidden. Update Elementor to 4.3.2 or later, or update Elementor Pro. If wp-admin is down, update over WP-CLI or replace the plugin folder over SFTP.
This one hit a lot of sites on the same day. Elementor 4.3.0 shipped on 22 September 2026, sites with plugin auto-updates on installed it overnight, and the next morning the front end and wp-admin both showed There has been a critical error on this website. The cause is a clash between the free plugin and older Elementor Pro releases, not anything you changed.
We still see it now on sites that skipped a few update rounds, on staging copies restored from September backups, and on client sites where Pro's license lapsed so Pro never updated. Below is how to confirm it, how to fix it with or without the dashboard, and the two other problems that tend to show up right after.
Applies to: WordPress 7.1, Elementor 4.3.0 and 4.3.1 with Elementor Pro 3.11 to 3.32. Fixed in Elementor 4.3.2 and later. Last verified: November 2026.
01Quick reference
| Error | Most likely cause | Try first |
|---|---|---|
| Dependency_Exception: hidden experiment | Elementor 4.3.0 or 4.3.1 with an older Pro | Update Elementor to 4.3.2+ |
| Global widget: only Advanced tab | Pro bug in the 4.3 cycle | Update Elementor Pro to 4.3.1+ |
| Unstyled pages after update | Stale cache or missing Elementor CSS files | Regenerate Files and Data, purge caches |
02The hidden experiment fatal error
Uncaught Elementor\Core\Experiments\Exceptions\Dependency_Exception: Depending on a hidden experiment is not allowed.
Quick fix: Update Elementor (free) to 4.3.2 or later. If wp-admin is down, run wp plugin update elementor --skip-plugins=elementor-pro or replace the plugin folder over SFTP.
Why it happens: Elementor 4.3.0 marked the nested-elements experiment as hidden and made the experiments manager throw an exception when any feature depends on a hidden experiment. Elementor Pro releases from 3.11 to 3.32 register a Menu (mega menu) module that declares that dependency. The check runs while Pro loads, before it looks at whether the feature is even turned on, so sites that never used the mega menu crash too. Elementor 4.3.1 did not change this. Elementor 4.3.2 treats a hidden dependency as satisfied, and Pro 3.33 dropped the dependency.
- Confirm it is this error. Turn on the debug log (see step 3 of our errors guide) or open the server error log and look for
Dependency_Exceptioninelementor/core/experiments/manager.php, withelementor-pro/plugin.phpin the stack trace. - If you can still reach wp-admin (some sites can, through the recovery mode link sent to the admin email), go to Plugins and update Elementor to 4.3.2 or later.
- If wp-admin is down and you have SSH, update Elementor while skipping Pro so the crash does not stop WP-CLI:
wp plugin update elementor --skip-plugins=elementor-pro. - No WP-CLI? Download the current Elementor zip from wordpress.org, unzip it on your computer and upload the
elementorfolder over SFTP or the host file manager, replacingwp-content/plugins/elementor. - Last resort to get back in: rename
wp-content/plugins/elementor-protoelementor-pro.off. The site loads without Pro features, you update Elementor, then rename the folder back and reactivate Elementor Pro on the Plugins screen. - Update Elementor Pro to its current release as well (this needs an active license), so the two plugins stay in step.
- Purge the page cache and the CDN, then load the home page, a Theme Builder template page and a page with a form while logged out.
# Update the free plugin without loading Pro
wp plugin update elementor --skip-plugins=elementor-pro
# Check both versions afterwards
wp plugin list --name=elementor* --fields=name,status,version --skip-plugins=elementor-proA plain wp plugin update elementor can fail on an affected site, because WP-CLI loads WordPress and the fatal error fires first. The --skip-plugins flag is a standard WP-CLI global option that stops the named plugin from loading for that one command.
Still broken after these steps?
Send us the URL and the exact error. Fixes start from $59, with a fixed quote within 24 hours and an NDA if you need it.
03If you would rather roll back
Updating forward is the better fix. A rollback is only worth it when a newer release breaks something else on a site you cannot test right now.
- If the dashboard works, Elementor has a built-in rollback under its Tools screen (the Version Control tab). Pick a version from before 4.3.0, such as 4.2.4, and reinstall it.
- If the dashboard is down, run
wp plugin install elementor --version=4.2.4 --force --skip-plugins=elementor-pro, or downloadelementor.4.2.4.zipfrom wordpress.org and replace the folder over SFTP. - Turn off auto-updates for Elementor afterwards (
wp plugin auto-updates disable elementor --skip-plugins=elementor-pro, or the link on the Plugins screen), or it will install 4.3.x again overnight. If auto-updates were already off, WP-CLI prints an error message that you can ignore. - Put a date in your calendar to update properly. An old Elementor release misses security fixes, so a rollback is a stopgap, not a fix.
Take a backup before any of this. If the site is down, a file and database backup from your host is fine. We cover the order of steps in our site broke after an update section.
04Two more problems that show up after the 4.3 update
Global widget shows only the Advanced tab (Content and Style missing)
Quick fix: Update Elementor Pro to 4.3.1 or later. Do not edit and save the global widget until the tabs are back.
Why it happens: A bug in the Pro release that shipped alongside Elementor 4.3 hid the Content and Style controls when editing a global widget. Elementor Pro 4.3.1 lists a fix for missing Content and Style controls on global widgets.
- Do not save the global widget while the tabs are missing. Every page that uses it would get the saved version.
- Update Elementor Pro to 4.3.1 or later from the Plugins screen.
- Clear the browser cache or open the editor in a private window so the old editor scripts are not reused.
- Open the page again and check that the Content and Style tabs are back before you change anything.
Pages look unstyled or half styled after the Elementor update
Quick fix: Regenerate Elementor's CSS files, then purge the page cache and the CDN.
Why it happens: Elementor writes each page's styles to CSS files under wp-content/uploads/elementor/css. After a big update or a rollback, cached HTML can still point to old CSS files, or the files get removed. Elementor Pro 4.3.0 also lists a fix for page CSS that could go missing after automatic CSS cleanup.
- In wp-admin open Elementor's Tools screen and click Regenerate Files and Data.
- Purge the page cache in your caching plugin (for example LiteSpeed Cache) and purge the CDN cache (for example Cloudflare).
- Check that Elementor and Elementor Pro are both on current releases, since a lone old Pro version is a common reason styles break.
- Load the page logged out in a private window. If only some sections are unstyled, open and update that page in the editor once.
- Still broken? Check the browser console for 404 errors on CSS files and confirm the uploads folder is writable (see uploads not writable).
05Stop the next Elementor update from taking the site down
This error is a good example of why Elementor and Elementor Pro should be treated as one unit. The free plugin auto-updated, Pro did not, and the mismatch crashed the site. On the sites we look after we follow a short routine:
- Update Elementor and Elementor Pro together, on staging first, and never let only one of them auto-update.
- Wait a few days on x.0 releases. Elementor shipped 4.3.1 and 4.3.2 within two days of 4.3.0.
- Keep the Pro license active on every client site. A lapsed license is the most common reason Pro falls behind.
- Keep the admin email current so WordPress recovery mode links reach someone.
- Keep SSH or SFTP details for every site in your password manager, so a fatal error is a ten minute job, not a ticket to the host.
If you saw Updating failed. The response is not a valid JSON response while saving in the block editor around the same update, that is a separate issue. Start with our invalid JSON fix.
If you run many Elementor sites for clients, our white label maintenance plans handle staged updates under your brand, and our Elementor development team can repair layouts that broke. For a one-off outage, use the WordPress error fix service.
Need the full list? See our WordPress errors fix guide and the hosting, PHP and cPanel errors guide.
More fixes
06FAQ
Why did my Elementor site crash when I did not update anything?
WordPress can auto-update plugins. If auto-updates were on for Elementor but Elementor Pro was older, the free plugin moved to 4.3.0 or 4.3.1 on its own and the mismatch caused the fatal error.
Does updating to Elementor 4.3.1 fix the hidden experiment error?
No. The fix arrived in Elementor 4.3.2. Any later release, including the current 4.4 line, also includes it.
Do I need an Elementor Pro license to fix it?
No. Updating the free Elementor plugin to 4.3.2 or later is enough, and that comes from wordpress.org. You should still renew Pro so it keeps getting updates and security fixes.
Can I just delete Elementor Pro to get the site back?
Do not delete it. Renaming the elementor-pro folder over SFTP stops it loading and keeps your Pro templates and settings in the database. Rename it back and reactivate it once Elementor is updated.
Will I lose my pages if I roll Elementor back?
No. Pages are stored in the database, and a rollback only swaps the plugin files. Take a backup first anyway, then regenerate Elementor's CSS files and purge caches after the rollback.






