How to load sliders on subsequent pages in GD Infinite Scroll?

Question

Here is my Testcase. If you scroll down, the feed will automatically extend: It is an infinite scroll-feed. However, the slider images of subsequent pages are not being loaded. As soon as the page is being refreshed, all visible sliders are loaded.

In the scenario I use the following two Drupal modules:

1. GD Infinite Scroll
2. Zurb Orbit

How can I get sliders of subsequent pages to work properly? (Additionally: If the last page is being scrolled down, the infinite scroll would literally keep scrolling this very page infinitely. Is there a way to prevent it and just stop upon hitting the last post of the last page?)

Answer 1

user gooddesignusa kindly showed me a solution:

scripts.js in the theme folder has to be like this (can also be created if no scripts.js is there):

(function ($, Drupal) {

  Drupal.behaviors.STARTER = {
    attach: function(context, settings) {
      // Get your Yeti started.
    }
  };

  //runs on document ready. 
    $(function(){
    //checks for autopager function and checks if ID of view is on page
    if($.autopager && $('#gelaendespiele').length){
      //binds ajaxSuccess 
      $(document).bind('ajaxSuccess.autopager',function(event, xhr, settings){
        //rerun function after ajax is done loading
        $(this).foundation('reflow');
      });
    }
  });

})(jQuery, Drupal);

Then I had to uncomment line 72 of my info file (make sure scripts.js is included)

Finally clear all caches.

Answer 2

The reason for this behavior is simple. Module uses ready-made JS libraries. It places them in the footer to make sure they will fire after elements meant to be affected are ready. But when other module dynamically adds elements, libraries are not fired again. This is a common problem with AJAX-loaded content and Drupal does have a solution for it.

The solution would be to wrap them in behaviors, as described in Managing JavaScript in Drupal 7. Not using behaviors actually can (and in my opinion should) be considered a bug against module compatibility. Sadly, doing it is too laborious task for Q&A format.