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
You could also try to find some "exclude" option at the plugin's settings, where you could exclude our files by file path:
If you are using WP Rocket, you might experience issues with its minification which changes the loading order of our files.
WP Rocket has an exclude option, where you should write this to the exclude css option:
/wp-content/cache/nextend/(.*).css /wp-content/plugins/nextend-smart-slider3-pro/(.*).css /wp-content/plugins/smart-slider-3/(.*).css
and this to the exclude js:
/wp-content/cache/nextend/(.*).js /wp-content/plugins/nextend-smart-slider3-pro/(.*).js /wp-content/plugins/smart-slider-3/(.*).js
WP Fastest Cache
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:
If that won't help, go to your Extensions → Plugins, filter out the "system" plugins and move the Nextend Smart Slider 3 and Nextend2 Library plugins 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.
Cloudflare’s Rocket Loader
data-cfasync="false"to them. Go to Global settings → Framework and find
Autoptimize and Litespeed cache
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.