Stable release. Please review.

No major bugs but some minor issues
1. It's better categorized as a views plugin.
2. I have a bottom border of every item.
On the first page, the border is displayed normally.
On the following pages, the border of the last item on each page disappears.

Also, we may need to add some option form to customize the infinite pager's behavior.
Like auto loading, limit of maximum pages etc.

My pager setting is 10 elements per page.
On pages other than the first one, "11" elements are displayed.
The extra element is located in the "More>>" div and can't be found in the page source.

Sorry, my own issue.
The module works great.

I think we can release a rc1. No major issues found in my testing.

Some issues here

1.
When i click the more link, the previous page will automatically scroll down a bit which will make users lose focus on where they were.
When tested on a more link in a view which is not located in the bottom of a page, everything's ok.
Seems to be an issue caused by the behaviour of removing footer text?

2. Occasionally, when i click the more link, all the page content will disappear for a second or two, and then reappear during the loading of the next page.

3. If you click the more link multiple times, multiple pages will be attached to the current one.
If you click three times, the next three pages will be loaded.

4. If i choose back to Full pager, the actual settings will be No pager. If i choose No pager, the actual one will be Full pager.
Seems that this module interferes the views' config form.

cerup, THANK YOU for taking this on. I haven't had any time to work on this module since releasing it (by request at DrupalCon), so I wasn't sure if I should have released it at all, but with you taking it on I'm glad I did.

I'd like to make you a full maintainer of the module, but when I try to give you access it says you don't have a CVS account. If you apply for one I'll vouch for you and you can officially take over the module from that point.
I also have my copy of the module in Git, at http://github.com/newleafdigital/views_infinite_pager, if you want I can give you access to that too.

I'll spend an hour or two on your module and the other issues in the queue today and hopefully will release it until you get a CVS account.

Thanks,
Ben

1. The fix doesn't work for me.
After the loading and attaching process, the whole page goes down like 30 pixels.

2. The js is fully loaded.
Normally, the browser loads the next page in the background and then attach the page.
But when i have this issue, the whole page content disappears in the loading process, and shows up after the browser finishes loading and attaching next page.

For #3, I came across #751208: ajax.module: An unknown error has occurred - when someone clicks 'submit' twice or more which allows "disabling the submit button when it's first click and enabling it back again when it has finished the request". I don't know anything about programming but posting just hoping that it is an idea that may apply.

I also use http://drupal.org/project/hide_submit module to disable submit buttons on forms.

I would like to help test when the next version is posted with the fixes mentioned above.

Thanks

table view with labels, every time when click the 'more' the label will show again.

FYI, I made cerup maintainer of this project.

Dunno if someone faced same problem as me but when the module is activated i can't disable paging anymore when i choose "no pager" it won't change and the full paging is activated maybe it's not related to this module but still that happens only when i activate views_infinite_pager

The one attached in #18 and i assume it's the latest one.

Thanks

Hi,

I used the zipped version in #18 also. While i get the infinite pager option in the pager selection in views, it doesnt work, for this option also the full pager gets switched on. Any help you can offer on this?

Thanks
Jaya

Sorry! My fault. Had not switched on Ajax. Now the more button works, but instead of the next 3 items coming below the first three like how it does in your squidy site, it replaces the first three. Could this be something in my sites css?

Thanks
Jaya

hi,

i installed this version of this module but i can't see it listed at my views...

how can i setup this module? views pager only shows full and mini.

thanks

Hi, i could install it trougth #18.
I have ajax and i see the more button, but it doesn't load with ajax, it sends a new request and the page refresh.

can someone helpe me?

thanks.

*edit*

I noticed that views_infinite_pager.js wasn't appearing at source code, so i manually add it and other views JS files, but it didn't worked it ajax. Although, no error was given.

Hum............i'm really not understaning this code...
where are you defining to use "alternateAjaxViewResponse" ??

and i don't know why even in the views ui admin area i can't see the js from this module been added...

Any clue?

i noticied that with garland theme this module is working properly.
But with my theme it isn't...i don't know what am i missing with my theme.
i saw some themefucntions in this .module file

what should be wrong? does anyone have an idea?

*EDIT: I found a solution, i had to use template php and a preproces page function where i embed the view*

Could you kindly share the code necessary. Thank you very much!

@yaz085: sure, here goes:
template.php :

function mythemename_preprocess_page(&$vars, $hook) {
  // Render the view.
  $vars['embedded_view'] = views_embed_view('name_of_view block_1');
   // Reload the JavaScript into the scripts.
  $vars['scripts'] = drupal_get_js();
}

then at your page.tpl you print the var:

<?php print $embedded_view; ?>

Hi , it seems as if the most development activity is going on in this issue. I just wanted to let you know that I posted a patch for a new feature in #968626: Automatically load next 'page'. I hope it can be included in the first stable version.

Hi, I don't get why the js is being attached in garland but not in my custom themes. I can't use the code in #35 because I'm not embedding views. Help.

Considering that this version is not in CVS yet I thought I'd file a bug report here. I'm not sure if this is an issue with Views Flag Refresh (project/views_flag_refresh) or this module yet however in combination the two produce some weird results. Views Flag refresh lets you ajax refresh a view upon hitting a flag link. If you have the two modules in use and hit a flag the view will refresh but with a huge gap (say 1000px) between the top of the view and the view content.

Hey, so I've run some more tests on this and it works great except I can't get it to work in any other theme than garland and I'm really not sure why. I've tried loading the javascript in on my page template or in my .info files but I'm still getting an "array" printout where the more button should be. Any help would be super appreciated.

Also, the js file shows up in the firebug but the view just ain't picking it up. Themes I'm using are based off of the tao or zen themes.

Ok, so I figured out that my custom themes were overriding the Views pager in a way that conflicted with this module.

But I have confirmed that there lies some sort of compatibility issues with the Views Flag Refresh module (http://drupal.org/project/views_flag_refresh). It appears as if the javascript breaks. I will investigate further and see if I can debug it but my skills are limited in this regard.

i'm not sue about your case, but just to remember, all js need to be added at template php file or page tpl.

subscribing

Hi, I try this module (#18) n have problem with image hover (hover preview modules). Image hover in next page same with image hover in page 1.

- http://drupal.org/project/hover_preview
- http://gochicorgohome.com/shop/15975,242,49668 (sites with hover image)

Any solutions?

Thx

Views Infinite Pager has issues with Calendar block (patched for AJAX support). When I click on next/previous buttons in the calendar, new block renders bellow the existing, instead of replacing the existing one.

Update:
I fixed it by changing the following code in views_infinite_pager.js: Drupal.attachBehaviors($view.parent());
to: Drupal.attachBehaviors($view);

@milosavlevski, thanks for sharing the solution to your problem.

I'm experiencing a similar problem whereby if a module needs to refresh a view (with Views Infinite Pager enabled) using ajax the refreshed view will be rendered below the current view. I tried your code alteration but this did not seem to help in my case.

I'm using three modules - Facebook-style Statuses, Views Flag Refresh and Views Display Tabs - that all use ajax to refresh the view.

I'm willing to put up a $60 bounty for anyone that can fix this conflict (the one I mention in comment #47) as I'm on a time-line here and require some assistance.

@cerup. You could consider my issue a feature request but it depends on how you look at the issue. I believe the expected behavior of using the views infinite pager is for the next view to be loaded underneath the current view. However, in my case and I assume in others' as well, I require the current view to be refreshed (not paged) by other means in a more typical fashion.

So let me describe my setup. I have a viewpage setup with tabs (for switching between displays via ajax); I then also use the Facebook-style status form at the top of the page (which upon submission refreshes the view); i the also use views flag refresh to allow users to flag content (which then refreshes the view to reflect changes). In each of these cases the expected behavior from the end user is to see the view in front of them refresh (be replaced not paged or loaded below the current view). Finally, views infinite pager is being employed to load the next page below the current view and so only in this instance should the expected behavior be to load the new view display below the current view. Just to be clear, I really am essentially replicating Facebook news feed like behavior with all these functions.

So, I believe what's happening (however I may be totally off since I'm not a good programmer but a themer) is that views infinite pager is overriding Ajax behavior of the view and hence preventing other calls to refresh the page via Ajax from simply refreshing the current view. What I require is for views infinite pager to only override the behavior of the paging aspect of te view and not every other attempt at refreshingita display. Does this make sense?

If you need any more help understanding this just check out: dev.londonfuse.ca. Make an account an try submitting a status or flagging content. I currenty do not have views infinite pager setup because of the overriding behavior.

Thanks

@cerup: the Calendar module doesn't provide an option to choose pager for a block view, because probably it uses it's own pager, instead of using the Views pager.

The version from #18 fixes the issues with Calendar, but it has problems with exposed filters. The fix you provided doesn't work. Continuing the discussion in #930754: view with exposed filters and infinite pager has a bug.

Ok, here we go:

• Calendar works fine.
• No page flickering.
• Exposed filters work fine.

There is a minor issue, as the module now renders just div.view-content, instead of div.infinite-page container, the fix you suggested in #21 doesn't work.

Great work cerup!