Troubleshooting
Slider Revolution AJAX Error: Causes and How to Fix It

Short answer
The Slider Revolution AJAX error means the plugin's background request to the server failed. It is usually caused by an outdated plugin, low PHP limits such as max_input_vars, a firewall block or a plugin conflict. Check the network tab, then update and raise limits.
Key takeaways
- The network tab shows the real status code behind the error.
- Outdated bundled copies of Slider Revolution are a common cause.
- Large sliders often need a higher max_input_vars limit.
- A 403 status usually means a firewall blocked the request.
- Stray PHP output from other plugins can corrupt the response.
What causes the Slider Revolution AJAX error?
The Slider Revolution AJAX error appears when the plugin's background request to admin-ajax.php fails or returns something it cannot read, usually because of an outdated plugin, low PHP limits, a security block or a plugin conflict.
Slider Revolution saves slides, loads templates and updates settings through AJAX. That means the editor sends a request to the server in the background and expects a clean reply.
If the reply is an error page, a PHP warning, a timeout or a block from a firewall, the editor shows an Ajax Error message instead of saving.
The good news is that the error almost always has a clear cause you can find in a few minutes.
| What you see | Most likely cause | Where to start |
|---|---|---|
| Error when saving a large slider | PHP input or memory limits | PHP settings |
| Error right after a WordPress update | Outdated Slider Revolution version | Update the plugin |
| Error with status 403 | Security plugin or server firewall | Firewall logs |
| Error with status 500 | PHP fatal error | Debug log |
| Error mentioning JSON or unexpected token | PHP notices or other output mixed into the reply | Debug log and conflicts |
| Error when importing templates | Server cannot reach the template server | Outgoing connections |
How do you see the real error behind the message?
Open your browser's developer tools, go to the Network tab, repeat the action that fails, and click the admin-ajax.php request to read its status code and response.
The message inside Slider Revolution is often vague. The network request tells you far more.
Follow these steps:
- Open the slider editor in Chrome or another modern browser.
- Right-click the page and choose Inspect.
- Open the Network tab and type
admin-ajaxin the filter box. - Trigger the error, for example by clicking save.
- Click the red or failed request and read the Status and Response.
Chrome's documentation on inspecting network activity explains the panel if you have not used it before.
The status code points you to the right section below. A 403 means blocked, a 500 means a PHP crash, a 504 means a timeout, and a 200 with odd text means extra output broke the reply.
Is your Slider Revolution version out of date?
An outdated copy of Slider Revolution is one of the most common causes, especially when it came bundled with a theme and has not been updated since.
Many premium themes include Slider Revolution. Bundled copies often do not update automatically unless the plugin is registered or the theme vendor ships a new version.
Older versions can break after a WordPress or PHP update because they use code the newer platform no longer supports.
To fix it:
- Check the installed version under Plugins.
- Compare it with the latest version on the Slider Revolution website.
- Update through your license, or download the latest copy from your theme vendor.
- Back up the site before updating, because major versions change the editor.
Also check that your theme is up to date. Theme vendors usually ship updated bundled plugins with theme updates.
Are PHP limits too low for your slider?
Yes, low PHP limits often cause the error when saving large sliders, because the save request sends many fields and needs memory and time on the server.
The settings that matter most are:
| PHP setting | What it controls | Common safe starting value |
|---|---|---|
memory_limit | Memory a PHP request can use | 256M or more |
max_input_vars | Number of fields a request can send | 5000 or more |
max_execution_time | How long a request can run | 120 seconds or more |
post_max_size | Size of the data a request can send | 64M or more |
upload_max_filesize | Largest file you can upload | 64M or more |
Large sliders with many layers can easily pass the default max_input_vars limit of 1000. When that happens, PHP quietly drops the extra fields and the save fails.
The PHP manual describes max_input_vars and other core settings.
You can usually change these in your hosting control panel. Our guide on raising the PHP memory limit shows the common methods.
The same panel usually controls upload size too, which our guide on increasing the max upload size covers.
Slider Revolution has a System Requirements area in its dashboard that shows whether your server meets its needs. Check it after any change.
Is a security plugin or firewall blocking the request?
If the request returns a 403 status, a security plugin, web application firewall or server rule like ModSecurity is probably blocking it because the slider data looks suspicious.
Slider data contains HTML, CSS and long encoded strings. Firewalls sometimes mistake that for an attack.
Try these steps:
- Check your security plugin's firewall log for blocked requests to
admin-ajax.php. - If you use Wordfence or a similar plugin, put the firewall in learning mode briefly while you save the slider.
- Check Cloudflare or your host's firewall for blocked events.
- Ask your host whether ModSecurity blocked the request, and give them the time it happened.
Our guide on setting up a web application firewall explains how allowlisting works.
Never turn the firewall off permanently. Find the rule that blocks the slider and add a narrow exception instead.
Is another plugin or the theme causing a conflict?
A conflict is likely when the response contains PHP warnings or HTML before the expected data, or when the error started right after installing or updating another plugin.
Any plugin that prints output during an AJAX request can corrupt the reply. Slider Revolution then sees something like Unexpected token in its JSON and reports an AJAX error.
Run a simple conflict test on a staging copy:
- Deactivate every plugin except Slider Revolution.
- Switch to a default theme if the error persists.
- Test saving the slider again.
- Reactivate plugins one at a time until the error returns.
Our full guide on fixing plugin conflicts has more detail, including how to test without affecting visitors.
Caching and optimization plugins are frequent suspects. They should not affect the admin, but some minify or combine settings do.
How do you check the PHP error log?
Turn on WordPress debug logging, repeat the failing action, then read wp-content/debug.log to see the exact PHP error that broke the request.
Add these lines to wp-config.php above the line that says to stop editing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Setting display to false keeps errors out of the AJAX response and the page, while still writing them to the log.
The official debugging in WordPress guide explains each constant. Our guide on reading the debug log helps you make sense of the output.
Look for errors that mention revslider or another plugin folder. Turn debugging off again when you are done.
Does your PHP version matter?
Yes, a PHP version that is too new for an old Slider Revolution release, or too old for a new one, can cause fatal errors that show up as AJAX failures.
Check your PHP version under Tools > Site Health > Info > Server. Then compare it with the plugin's stated requirements.
If you recently upgraded PHP and the error started then, update Slider Revolution first. Rolling PHP back should be a short-term step only.
Our guide on WordPress PHP compatibility explains how to check plugins before changing versions.
Why does the error appear when importing templates?
Template imports fail with an AJAX error when your server cannot download files from the Slider Revolution template server, often because of an unregistered license, a firewall on outgoing connections or a timeout.
Premium templates usually need an activated license. Bundled copies from a theme often cannot import premium templates on their own.
If you are registered and imports still fail, ask your host whether outgoing HTTPS connections are allowed. Also raise max_execution_time, since large template packs take time to download and unzip.
What if nothing fixes the AJAX error?
If the error remains after updating, raising limits, checking the firewall and testing conflicts, collect the network response and debug log and send them to Slider Revolution or your theme's support team.
Include these details in your ticket:
- WordPress, PHP and Slider Revolution versions.
- The exact action that triggers the error.
- The status code and response text from the network tab.
- Relevant lines from the debug log.
- Whether the error happens with all other plugins off.
If you only need a simple slider, a lighter alternative may also be worth a look. Our guide on using Smart Slider in WordPress covers one option.
For other Slider Revolution problems, see our guide on the preview not working.
If slide buttons do nothing when clicked, read our guide on button links not working.
Frequently asked questions
What does Ajax Error mean in Slider Revolution?
It means the editor sent a background request to the server and did not get a valid reply. The request may have been blocked, timed out or returned a PHP error. The network tab in your browser shows the exact status code and response.
How do I fix the AJAX error when saving a slider?
Update Slider Revolution, then raise PHP limits such as memory_limit, max_input_vars and max_execution_time. Large sliders send many fields, and low limits make the save fail. If it still fails, check your firewall log and run a plugin conflict test.
Why does Slider Revolution show an AJAX error after a WordPress update?
Older plugin versions can break with newer WordPress or PHP releases. This often happens with copies bundled in a theme that never received updates. Update the plugin through your license or get the latest bundled copy from the theme vendor.
Can Wordfence cause the Slider Revolution AJAX error?
Yes. Slider data contains HTML and long strings that a firewall can mistake for an attack, which returns a 403 status. Check the firewall log, use learning mode briefly while saving, and add a narrow exception rather than turning the firewall off.
Do I need a license to fix the AJAX error?
Not always. Limit, firewall and conflict fixes work without one. However, updating the plugin and importing premium templates usually need an activated license, or an updated copy supplied with your theme.
Sources
- Inspect network activity Chrome for Developers
- Debugging in WordPress WordPress.org
- Description of core php.ini directives PHP.net
- AJAX in plugins WordPress Developer Resources
- Slider Revolution ThemePunch
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


