Cache or Minification

In this article

Slider only show up correctly for logged in users, not for logged out users

When you are seeing differences between logged in and logged out users, that always means a cache plugin problem. Cache plugins are working that way, that you are seeing the not cached version when you are logged in, but the cached version where you are logged out. You should try to clear the cache of your website's caching plugin and if that wouldn't work, search for the name of your cache plugin in our documentation in case you find one specifically for that plugin.

We're storing one version of the slider, so if you make changes to the slider, but it doesn't show up that also happens because of a 3rd party cache. Make sure you clear your cahce plugin's cache after every change you make in the slider.

Problem with minifications

Our code usually works with most JavaScript and CSS merging and minifying plugins/extensions, but not all plugin does. If they have an error, that will cause an error in the whole merged file including our code. You should just turn off your JavaScript, CSS merge, minification in your plugin, or delete the plugins causing troubles, or contact the developer of your minifying plugin!

You could also try to find some "exclude" option at the plugin's settings, where you could exclude our files by file path: wp-content/cache/nextend

WP Rocket WordPress

If you are using WP Rocket, you might experience issues with its minification which changes the loading order of our files.

To find the minification/optimization settings of WP Rocket, you have to go to your left WordPress admin menu's Settings → WP Rocket → File Optimization.

There you will find a  Load JavaScript deferred option, which is not compatible with our codes, so you have to turn it off.

WP Rocket also has an exclude option, where you should write this to the Excluded CSS Files option:


and this to the Excluded JavaScript Files:

Also write this to the  Excluded Inline JavaScript:
These are the places from where we are calling in our files, so this should make the minification to skip them.

If the problem still persists, go to the Framework Settings and under the JavaScript part turn on the Async option, also under the CSS part turn on the Async option.

WP Fastest Cache WordPress

If your Smart Slider doesn't work with the CSS and JS minification of WP Fastest Cache, then you could  exclude our files from WP Fastest Cache by adding these wordsto the CSS and JS url containment exclusion:

  • nextend
  • smart-slider3
  • smart-slider-3

If that won't be enough, turn on the Async option at our Global Settings for both the JavaScript and CSS files.

JCH Optimize

Our slider should work with JCH Optimize, so what you should do is first try to turn on the "Async" option at the Javascript options, maybe at the CSS part too at our Global Settings. This will call in our files differently, so maybe JCH Optimize will skip them this way.

If that won't help, go to your Extensions → Plugins, filter out the "system" plugins and move the Smart Slider 3 System Plugin plugin before JCH Optimize. This is the order of how codes are running on your website, and this could also make JCH Optimize to skip our codes.

Nitropack WordPress

Nitropack's optimization might cause problems with the slider. Visit and find Excluded Resources (Images, JavaScript, CSS, etc.). Press Add an Exclude and fill it the following way:

Asset URL/Code Resource Type Resource Relation Device Excluded Operations
SmartSlider3 JavaScript Any Resource Relation Any Device All Operation
_N2 JavaScript Any Resource Relation Any Device All Operation

As you can see on the screenshot below

Cloudflare’s Rocket Loader

Rocket Loader from Cloudflare is calling in the JavaScript files after everything else has been loaded, but because of this a lot of JavaScript events are skipped, which are used by many JavaScript developers, so complex codes like ours aren't working with it, and you shouldn't use it.

But according to this article the loaded scripts can be ignored by giving data-cfasync="false" to them. Go to Global settings → Framework and find Script attributes under JavaScript and write this to the field:

Autoptimize and Litespeed cache WordPress

Both Autoptimize and Litespeed cache seems to have an option for  Critical CSS. This isn't compatible with our slider, so you should turn it off.

Autoptimize WordPress

You can try to exclude our CSS and JS files from Autoptimize's minifications by adding our folder to the exclusion list:

Free Smart Slider 3:

Pro Smart Slider 3:


Autoptimize's Aggregate CSS-files? option prevents the fonticons from loading properly. To solve the problem, you should write the following to the Exclude CSS from Autoptimize: field:

fontawesome.min.css, icomoon.min.css, linearicons.min.css, materialicons.min.css, typicons.min.css

Then go to Global settings → Framework and enable Async non-primary CSS to async the fonts from our end.

SG Optimizer WordPress

SG optimizer's Combine CSS Files option causes some of our files not to be called in, as it skips codes for some reason. Turn off SG OptimizerFrontend OptimizationCombine CSS Files and it should solve the problem.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.