It's difficult to describe the entire scenario for this problem so I'll just list the steps to reproduce:
1. Create a Single Frame Views Slideshow view that has two "Block" displays.
2. Turn on AJAX pagination in both displays.
3. Turn on both blocks on the same page.
4. Click on the second slideshow's "next" button.
5. Instead of the second slideshow's thumbnails being updated, the thumbnails in the first slideshow are doubled up. The second slideshow's thumbnails are lost.
What causes this (as far as I can tell): Views does an AJAX request and gets back the new HTML. It actually updates the correct slideshow on the page. However the problem is that the generated HTML has the wrong ID. Views Slideshow expects id="views_slideshow_singleframe_main_2", but the returned slideshow has id="views_slideshow_singleframe_main_1". Then when the JavaScript executes it gets the wrong ID (1 instead of 2) and then it attaches all the behaviors on the wrong slideshow.
My guess is that there is some static variable that Views Slideshow is depending on to count the number of slideshows. However on the AJAX request only one slideshow is generated, so the ID for the slideshow is always 1, even if the ID on the original page was something higher, because there were multiple slideshows on the same page.
Comments
Comment #1
redndahead commentedack this is going to be a pain to debug. Curiously is there a reason you are using ajax pagination over the pager that's available through the settings? Are the number of items too large?
Comment #2
quicksketchredndahead: Yes we expect to have several pages (three or more likely). The lists themselves contain hundreds of items. Though as you suggest, for the mean time we may have to forgo paging. We don't want to load unnecessary thumbnails since the site is anticipating multi-million page-views on the front page that contains this rotator, so loading 5 (or more) unnecessary thumbnails would not be a good option for us.
Comment #3
redndahead commentedMarking this as a duplicate of #323366: Views Slideshow: Ajax loading support More comments there and I think fixing that will fix this issue.