Endless pagination loads entire page contents on scroll

[sparkplugmarcus]

Thank you for the great app!

The initial view of the page works fine, but once scrolled a the entire page contents are loaded into the endless_page_template div.

The relevant parts of my view are below. I'm using a CreateView because I have the comments form on the same page as the paginated comments.

class MyIndex(CreateView):
    form_class = CommentForm
    template_name = 'my/index.html'
    page_template = 'my/comments.html'

    def get_context_data(self, **kwargs):
        context = super(MyIndex, self).get_context_data(**kwargs)
        context.update({
            'comments': Comment.objects.order_by('-id').filter(parent=None),
            'page_template': self.page_template,
        })

        return context

The relevant parts of my/index.html template (main template)

<script src="/static/endless_pagination/js/endless-pagination.js"></script>
<script type="text/javascript">
    $.endlessPaginate({
        paginateOnScroll: true
    });
</script>

<div class="endless_page_template">
    {% include page_template %}
</div>

The relevant parts of my/comments.html (page_template)

{% load endless %}

{% paginate comments %}
{% for comment in comments %}
    <span class="lead">{{ comment.name }}</span>
    {{ comment.message}}

    {% if not forloop.last %}
        <hr />
    {% endif %}
{% endfor %}
<br />

<div class="row-fluid">
    <div class="span8 offset2 pagination-centered">
        {% show_more %}
    </div>
</div>

[macdhuibh]

Looks like we're experiencing the same issue while using AjaxListView.
Did you ever find a fix / workaround?

[sparkplugmarcus]

No, I'm just decided to not use scrolling. I posted a question on SO, but no answer.

http://stackoverflow.com/questions/20485004/endless-pagination-loads-entire-page-contents-on-scroll

[ghost]

FWIW, I just encountered the same issue when I wrote:

{% paginate object_list using 'page_number' %}

putting the 'page_number' in quotes.

[suchanlee]

Although the issue seems to have been posted a month old, I ran into the issue as well several months ago and found that the problem was in evaluating the screen size. I'll take a further look at my fix and submit a pull request