Interesting problem…..It looks like the Owl Carousel is not behaving properly, but I can’t see how my plugin could cause that. I’ll have to do some deeper investigation on that, have you checked any support for Owl? Maybe they have an idea?
Thread Starter
lkung
(@lkung)
Thanks for checking! I’ve submitted a support request with Owl and will let you know if they have any suggestions or find anything.
Thread Starter
lkung
(@lkung)
Update: it looks like an issue with both plugins using the term “cloned”. If the page is refreshed below the Sticky Element, the carousel’s cloned elements are correct. But then if you scroll up on the page past the top of the Sticky Element, the carousel’s cloned elements disappear (I’m using Dynamic Mode). If I uncheck Dynamic Mode, the carousel’s cloned elements stay around, but then its CSS is messed up. I’ll keep looking to see what else is causing a conflict between the two plugins.
Hmmmm. If the Owl carousel indeed uses the “cloned” class, then I can see why the conflict would occur. Good find! I will create a version of the plugin for you that doesn’t use that classname and then we can check if that solves the problem.
I should have this ready for you after some testing, so let’s say tomorrow morning.
Thread Starter
lkung
(@lkung)
That would be great — thanks! I’ll update this ticket with anything else I find in the meantime.
Thread Starter
lkung
(@lkung)
Looks like that did the trick. I replaced all instances of “cloned” with “clonedsticky” in jq-sticky-anything.min.js and it works fine now. Thanks for the great plugin!
Glad that worked! Keep on using that modified version for now. I will fix this in the next release, so when you do get an update notification and you update the plugin, your modification will be overwritten but it will be pretty much the same as what you did.
Thanks for your help!
Thread Starter
lkung
(@lkung)
(Marking this as resolved)
