WordPress 6.9 Broke Slider Revolution — Fix with 7.0.10 (Step by Step)

You updated to WordPress 6.9 "Gene" and now every Slider Revolution module on your site is a ghost: the background video or image plays full-width, but all the rows, headlines, CTA buttons and text layers are gone. The browser console shows Uncaught TypeError: Cannot read properties of undefined (reading 'getAllSliderAliases'), wp-admin throws "There has been a critical error on this website", and you got an email from WordPress titled "Your Site is Experiencing a Technical Issue". Good news — there is exactly one fix that works, shipped April 22, 2026: Slider Revolution 7.0.10. Below: why it broke, how to update, and what to do if your theme bundles SR or wp-admin is locked.

mysite.com

⚠ Slider Revolution broken after WordPress 6.9

Uncaught TypeError: Cannot read properties of undefined
(reading getAllSliderAliases)
in jquery.themepunch.revolution.min.js

Plugin: Slider Revolution 7.0.8 · WordPress 6.9 · Layers not initialized

mysite.com — Home

HomeAboutShop

✓ Slider Revolution patched · layers rendered

Design Without Limits

Fully animated hero — slides, layers, parallax, CTA. Back online after the 7.0.10 update.

Get Started →

Slider Revolution 7.0.10 · WordPress 6.9 ✓

Comment×

Update Slider Revolution|

Fix it ⟳ ✓ Done

SimpleReview PRO

waiting for selection…

Detected

MissinggetAllSliderAliases

Pluginrevslider 7.0.8

Fix plan

Bump revslider 7.0.8 → 7.0.10 (WP 6.9 compat, Apr 22, 2026) + clear object cache

Result

Layers render. wp-admin unlocked. WP 6.9 retained.

✓ PR opened

chore: bump revslider 7.0.8 → 7.0.10
composer.json · +2 lines

Click SimpleReview → select the broken slider → Fix it → layers back without rolling back 6.9

Why WordPress 6.9 Broke Slider Revolution

WordPress 6.9 "Gene" shipped on December 2, 2025. Three internal changes landed together that touch how Slider Revolution boots:

• WP_Query cache key generation was reworked. Anything that pre-warmed slider aliases against an old cache signature now misses on the first request.
• The Abilities API was introduced, modifying how plugins register internal capabilities during boot.
• The Interactivity API was modified, which affected how layer-level JS bindings are hydrated in the browser.

Inside Slider Revolution, the team had started a multi-release internal refactor. In the 7.0.8 cycle, the private method getAllSliderAliases() was removed from the plugin's JS API as part of the WP 6.9 compatibility work. But any third-party theme or companion plugin (and SR's own older bootstrap path under WP 6.9's new Interactivity API) that still calls getAllSliderAliases() throws the fatal below — and because it throws during slider initialization, every layer after the background fails to render:

Uncaught TypeError: Cannot read properties of undefined (reading 'getAllSliderAliases')
    at RevSlider.init (revslider/public/assets/js/rbtools.min.js:14)
    at HTMLDocument.<anonymous> (revslider.min.js:2)

Slider Revolution 7.0.9 (April 17, 2026) was a partial backward-compat restore — the changelog reads "Fixed a backward compatibility issue caused by themes/plugins calling the removed getAllSliderAliases() function". That helped some users but did not fully resolve the 6.9 interaction. Five days later, 7.0.10 (April 22, 2026) shipped as the first officially WP 6.9 compatible release; the official changelog states: "7.0.10 is WordPress 6.9 compatible".

Diagnose: Exact Error Messages You Should See

Before you fix anything, confirm the symptom matches. Add these lines to wp-config.php (above the "That's all, stop editing" comment):

define( 'WP_DEBUG',         true );
define( 'WP_DEBUG_LOG',     true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Reload the broken page. Then cross-reference these signatures:

If at least two rows match, you have the WP 6.9 × Slider Revolution break. Move to the fix paths below — rank 1 → 2 → 3 exactly in this order.

Fix 1: Update Slider Revolution to 7.0.10 (Primary Fix)

If you can still reach wp-admin, this is the two-minute path and the fix for 95% of sites. Slider Revolution 7.0.10 (released April 22, 2026) is the first officially WordPress 6.9 compatible version.

1. Log into wp-admin. Go to Plugins. If WordPress shows an "Update available" notice next to Slider Revolution, click Update Now.
2. If no update notice appears (common on licensed installs), go to Sliders → Globals → Register Plugin. Confirm the purchase code is green, then click Check for Updates and pull 7.0.10 or newer.
3. Confirm the new version in Plugins — the line should now read Slider Revolution 7.0.10.
4. Move immediately to Fix 2 (clear all caches). Do not skip — SR ships a persistent cache that survives the update.

No dashboard update button / license expired? Download the 7.0.10 standalone ZIP from your ThemePunch account and FTP-replace /wp-content/plugins/revslider/ (see Fix 3). If the license is truly expired, ThemePunch sells renewals at roughly $29/year; without it you cannot receive future updates, but 7.0.10 itself can be installed from the existing download.

Fix 2: Clear All Caches (Mandatory)

This is the step every rushed fix guide skips and every support thread eventually reveals as the missing piece. Slider Revolution caches its rendered slider output per-version, and that cache survives the plugin update. Layered on top of it:

1. Slider Revolution cache — wp-admin → Sliders → Globals → Tools → Clear All Caches (empties SR's own rendered-output cache).
2. WordPress plugin cache — WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache: purge all. Object cache (Redis/Memcached) included.
3. Server cache — Varnish, Nginx fastcgi_cache, OPcache. If you don't manage the server, ask the host to purge.
4. CDN cache — Cloudflare (Caching → Purge Everything), BunnyCDN, Sucuri, StackPath.
5. Browser cache — hard reload (Ctrl+Shift+R / Cmd+Shift+R) or open an incognito window.

Fix 3: No Dashboard Access — FTP Replace or Core Rollback

Use this only when wp-admin is unreachable (stuck on "There has been a critical error on this website" and refresh doesn't help). Two options, in order of preference.

Option A: FTP-replace the plugin folder (recommended)

Keeps you on WP 6.9 (including its security patches). Requires a 7.0.10 ZIP in hand (download from a working environment or a teammate's ThemePunch login).

1. Download the Slider Revolution 7.0.10 standalone ZIP. Unzip locally — you should get a revslider/ folder.
2. Connect over SFTP. Navigate to /wp-content/plugins/.
3. Rename the existing folder to revslider.old (do not delete yet — it's your rollback).
4. Upload the new revslider/ folder in full.
5. Reload wp-admin. The critical error should clear. Now run Fix 2 — clear all caches.
6. Once the site is verified working, delete revslider.old.

Option B: Rollback WordPress core to 6.8.2

Last resort — buys you 30 minutes while you sort out the SR update. You lose the WP 6.9 security patches until you update again.

1. Over FTP, drop the WP Downgrade plugin into /wp-content/plugins/.
2. FTP-rename revslider to revslider.disabled so WordPress auto-deactivates it — wp-admin comes back.
3. wp-admin → Settings → WP Downgrade → WordPress Target Version: 6.8.2.
4. Dashboard → Updates → Re-install Now.
5. Rename revslider.disabled back to revslider. The slider renders again on 6.8.2.
6. Get a 7.0.10 ZIP, update Slider Revolution, then move back to WP 6.9 via the same WP Downgrade flow (target version empty → latest).

Theme-Bundled Slider Revolution — The Hard Case

A large fraction of WP 6.9 × Slider Revolution casualties can't follow Fix 1 at all, because their theme bundles Slider Revolution. Themes that commonly bundle SR include:

• X Theme / Cornerstone (ThemeCo)
• Avada (ThemeFusion)
• Salient (ThemeNectar)
• BeTheme (Muffin Group)
• Enfold (Kriesi)
• Bridge, Jupiter, The7, and many other ThemeForest bestsellers

In these themes, SR ships inside the theme's plugins/ directory and the theme's functions.php registers a version guard. When you click "Update" from the Plugins page, the theme immediately overrides back to the bundled version. You have two workarounds:

Option A: Wait for the theme vendor update

The clean path. After an SR release, the major themes typically ship a bundling update in 1–4 weeks. Subscribe to your theme's changelog or support forum. X Theme, Avada and Salient usually move fastest.

Option B: FTP-replace /wp-content/plugins/revslider/ manually

Follow Fix 3 Option A above. Caveat: when you next update the theme, its bundled SR may either (a) overwrite your manual 7.0.10 with the older bundled version, or (b) the theme's version check may fail and flag a warning. Keep the 7.0.10 ZIP handy so you can re-apply after every theme update, and budget five minutes per theme update to re-verify the SR version.

Version Compatibility Matrix

How SimpleReview Automates This

Diagnosing "only background video renders" manually, matching it to the getAllSliderAliases fatal, and deciding between plugin update / FTP replace / theme vendor wait takes 20–30 minutes the first time. SimpleReview collapses it into one click:

1. Install the Chrome extension and open your broken page.
2. Click the SimpleReview icon, then click the empty hero area.
3. Type "Slider Revolution broken after WP 6.9 — only background video shows" and click Fix it.
4. SimpleReview reads revslider.php to confirm the installed version is 7.0.8, pulls debug.log over SFTP to confirm the getAllSliderAliases fatal, checks whether SR is standalone or theme-bundled, and opens a PR with the right action — composer.json version bump for standalone, or an FTP-replace plan + theme-vendor-tracking issue for bundled installs.

Frequently Asked Questions

Related WordPress Fixes

Sources

• make.wordpress.org/core/ — WordPress 6.9 "Gene" field guide (Dec 2, 2025)
• Slider Revolution official changelog — 7.0.8, 7.0.9, 7.0.10 release notes
• wordpress.org — Slider Revolution support forum (WP 6.9 compatibility threads)
• wordpress.org — WP Downgrade plugin
• wordpress.org — Debugging in WordPress (WP_DEBUG_LOG)