Update View Result Summary after loading more content with Ajax enabled

Try the patch have made changes to remove the headers in table format repeat on load more, in addition to the patch in #10 to replace the header and footer of the view.

Patch #14 is dirty with comments that should not be merged. Could we have an interdiff with #12 please or which patch should we proceed with?

Is this still an issue with 2.0.x? If yes, please update the version and set the status active again with clear steps or (best) with a test showing what's broken.

If nobody replies, we should assume this is fixed and close this issue outdated.

Thanks!

The latest patch #14 is incompatible with the latest version 2.0.2

#10 is compatible but showing wrong results

I have updated the patch for D10.
Request everyone to review it once.

Hi Guys,
I'm also facing a similar issue on the views page, but in my case, with full pager and ajax option enabled, if I click on "View pager," which jumps to the top of the page, no new items are shown. Everything is looking fine; no errors are coming. Additionally information Drupal version is 10.2.0.

Eugene Bocharov → made their first commit to this issue’s fork.

Merge request #24 based on patch from #10 with some changes:

• using data-* attributes instead of CSS classes for header and footer area to keep consistency with views content selectors
• JS code improvements without changing the logic
• added comment about using @start token in README

Using @start token with infinite scroll module looks like non-trivial task. Actually @start on infinite scroll views can be 0, 1 or another number if query has page parameter and thus view initially has offset. As on AJAX request for load more views still gets from database not all records but only next range of items it make sense that @start is replaced with offset on the back-end. And as soon as the views_infinite_scroll does not replace items but append them on the front end using JS, probably it would be better to control those tokens on the front end as well. It might be possible if tokens had some wrappers but they don't have. So for now I would suggest just not use @start token in infinite scroll views and use something like Displaying @end of @total

Attaching patch file in addition to MR for 2.0.x.

I used patch #25 and works perfectly. Will have to find a workaround for using the @start token though.