Hi Mike,
You switch to version 2 of JQuery Cycle on the Rotating Tweets settings page when you switch to version 2 of the JavaScript.
It may not work though because Cyclone Slide 2 also uses version of JQuery Cycle…
Please let me know what happens!
Martin
Hi Martin,
The rotating tweets widget wasn’t working with Cyclone Slider 2 on version 1 of the JQuery cycle but does work with version 2.
– Mike
I’ll see if I can make it automatically adjust to version 2 if Cyclone Slider 2 is present.
Martin
I’ve been having the same problem, only when I switch Rotating Tweets to use cycle2, my next / prev buttons on my cyclone slider flash the next slide and skip to the one after that (though it works fine on autoplay). I’ve tried deregistering RT scripts but I’m afraid it’s a bit above my head. Any suggestions would be mightily appreciated (and do let me know if you need additional info)
~ Mor
I’d really need to see the page. The cycle is triggered by HTML code on the page and it sounds like the code for Cyclone Slider might be clashing with the Rotating Tweets code.
Thanks… as it’s still in development is there a way I can send it to you privately?
Sure. My contact details are accessible via http://www.martintod.org.uk
The issue is that jquery-cycle2 is being loaded twice – once by RT and once by Cyclone Slider 2.
I need to take a quick look at how Cyclone Slider 2 uses it. There may be a quick fix here. I’ll take a look.
Martin
Thanks Martin,
I’ve sent you an email.
I think the solution in the development version may solve your problem.
In essence, it uses the Cyclone Slider 2 scripts instead of the Rotating Tweets ones (lines 1763-1769 if you’re interested)!
Yay! The scripts were being loaded twice with this new code, though… So I removed the 3 lines that loaded the cyclone scripts, and also made sure the Rotating Tweets scripts are being loaded in the footer and Cyclone scripts in the header (otherwise rotating tweets wouldn’t work). I just copied those few lines into rotatingtweets.php and added rotatingtweets_v2_cyclone.js into the plugins js folder… Will this be part of your next plugin update? I ask because I’m wondering what will happen if I update the plugin via WordPress on the next release.
I’ve played around with it to try and stop it loading everything twice (but you might want to save your version before trying it!).
I will be keeping the changes in the next ‘official’ version.
Works great! Thanks for this!
