After updating one of my sites to V6.0.2, the Cornerstone Slider is behaving in Marquee mode. See video in the secure note.
In the video you can see the different speeds of the slider, triggered only by scrolling up and down the page! Sometimes it even runs backwards!
Hi @Regnalf,
Thanks for reaching out.
I have checked your website and found that the autoplay attribute value is set to Marquee and that is why it acts like that. But didn’t find the issue you have shown in the video. If you haven’t set it to Marquee, but are still it set to that, there might be some different reasons behind your issue. I would like to suggest troubleshooting the following common issue to help us to recognize the reason.
If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins.
If none of the above help, please provide login credentials for your site in a secure note to examine it further, including:
– WordPress Site URL & Login URL
– WordPress Admin username/password
To create a secure note, click the key icon underneath any of your posts.
Thanks
I’ve set nothing special in this slider.
It was working smoothly in version 5.1.5. and it’s saddly one more thing that’s broken after upgrade to version 6.
And the drag functionality also didn’t work well as in the previous version.
Transition needs to be set to “Linear” to work properly in Marquee mode. That really should be the default there. In general marquee mode needs some performance work. Drag issues with sliders has been noted. Thanks apologies for the annoyances.
I set it to Linear, but it still have some issues. Hope you will release a fix soon.
Many Thanks @charlie
I was having this same issue but managed to resolve it by setting the transition to linear and setting the transition speed to 0ms. Possibly it works for you as well!
Hey guys,
Thank you for sharing your thoughts, we really appreciate your help.
Cheers!
I just wanted to report the same issue with multiple installs of Pro. I have tried lots of fixes, but I’m pretty sure this is a bug. If this could be a priority fix for the next roll out, that would be great. Thanks.
Hey @littleshock,
Our developers are already aware of the issue. Rest assured that they will fix it but we don’t have any ETA.
Thank you.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
