Hello,
Are you using like this :
[slick-slider dots="false"]
Please do not copy and paste the code directly from here. First add in to some notepad and then add in to editor OR manually add the parameter ie dots="false".
yes, that’s what I am using. Instead I have to add a css styling display:none to hide them.
dots=false is the default according to the documentation
Hello,
Does your problem solve or not?
Thanks
no. Adding the attribute does not make any difference. I have no js errors being reported in the console either.
Hello @aurovrata
Can you please share your website link?
sure, here it is.
If you inspect either slider on the side of the central image with the button ‘Free Valuation’ you will seen the the ul.slick-dots element has a display:none styling…but in Firefox this still displays the button elements embedded in the list elements.
I checked on Chrome, and the issue is the same
Hello,
We have checked our end it’s working fine.
We have checked your site slider currently dots is true https://nimb.ws/XfsBuw
You can use this parameter [slick-slider dots="false"] for remove
but please do not copy and paste the shortcode write manually some time quotes(“) causing an issue.
Thanks
my slider shortcode is set to:
[slick-slider category=38 arrows=false autoplay_interval=4000 speed=2000 fade=true dots=false]
makes no difference.
Playing around with the shortcode, I realised that putting dots=false as the first attribute makes all the difference… it now removes the dots.
[slick-slider dots=false category=38 arrows=false autoplay_interval=4000 speed=2000 fade=true]
strange!
Hello,
Also, look like you have not used quotes in parameter dots="false"
Thanks
-
This reply was modified 7 years ago by
Rafik.
Also, look like you have not used quotes in parameter
quotes are not required! You only need quotes when you have space characters in your attribute values. Furthermore, integer values need to be unquoted to make sure they work, as your plugin does not cast string values to integers.
I realised that putting dots=false as the first attribute makes all the difference
this still means that your plugin has a bug, since it should not make a difference the order in which the attributes are placed in the shortcode.
