I can’t replicate this (but am using IE10).
What happens if you open the console [hit F12 to open developer tools on IE10, then the ‘script’ tab)? Are there any relevant error messages in the JavaScript console?
The only thing I can think of looking at your code is to add widget or widget %2$s to the class variable of the 'before_widget'(?) call in your 'register_sidebars' command to change from:
'<li class="widget1">'
to:
'<li class="widget1 widget">'
or
'<li class="widget1 widget widget_rotatingtweets_widget">'
Finally, what happens if you switch off WP_DEBUG ? I’ve put in quite a few debug messages – and one of them may be accidentally triggering something – and I may need to cut them back.
One more thought… what happens if you go back to using version 0.625 of the Javascript?
Thank you for your quick reply.
Reverting to version 0.625 fixes the problem.
Adding the following classes while using version 0.709 does not work.
<li class=”widget1 widget widget_rotatingtweets_widget”>
F12 tab results on version 0.709:
LOG: rt_target_width = 250
LOG: [cycle] terminating; zero elements found by selector
Weirdly, turning on debugging seemed to make it work but now if I turn off debugging it still works so I don’t think that was the problem.
So, currently it is working using 0.709 but I’m not clear why this changed…
Please let me know what I can do to help you further with this.
Glad it’s working now.
The rt_target_width = 250 means it’s now using the width of the container to set the width of the rotating tweet (which is probably a good thing).
Strangely, I’m not getting the LOG: [cycle] terminating; zero elements found by selector message when I look at other sites using Rotating Tweets with IE – so there’s clearly still something odd going on – but there’s nothing I can obviously spot. It might be worth having a look to see if any other script includes a reference to .cycle(). It’s the only other thing I can really think of!
