linaro-django-pagination allows for easy Digg-style pagination without modifying your views.
There are really 5 steps to setting it up with your projects (not including installation, which is covered in Installation.)
List this application in the INSTALLED_APPS portion of your settings file. Your settings file might look something like:
INSTALLED_APPS = (
# ...
'linaro_django_pagination',
)
Install the pagination middleware. Your settings file might look something like:
MIDDLEWARE_CLASSES = (
# ...
'linaro_django_pagination.middleware.PaginationMiddleware',
)
If it’s not already added in your setup, add the request context processor. Note that context processors are set by default implicitly, so to set them explicitly, you need to copy and paste this code into your under the value TEMPLATE_CONTEXT_PROCESSORS:
("django.core.context_processors.auth",
"django.core.context_processors.debug",
"django.core.context_processors.i18n",
"django.core.context_processors.media",
"django.core.context_processors.request")
Add this line at the top of your template to load the pagination tags:
{% load pagination_tags %}
Decide on a variable that you would like to paginate, and use the autopaginate tag on that variable before iterating over it. This could take one of two forms (using the canonical object_list as an example variable):
{% autopaginate object_list %}
This assumes that you would like to have the default 20 results per page. If you would like to specify your own amount of results per page, you can specify that like so:
{% autopaginate object_list 10 %}
Note that this replaces object_list with the list for the current page, so you can iterate over the object_list like you normally would.
In general the full syntax is:
autopaginate QUERYSET [PAGINATE_BY] [ORPHANS] [as NAME]
Now you want to display the current page and the available pages, so somewhere after having used autopaginate, use the paginate inclusion tag:
{% paginate %}
This does not require any arguments, but does assume that you have already called autopaginate, so make sure to do so first.
That’s it! You have now paginated object_list and given users of the site a way to navigate between the different pages–all without touching your views.
By default the objects will be paginated using a helper template “pagination/pagination.html”. You can change this with an argument to paginate.
In general the full syntax is:
paginate [using "TEMPLATE"]
For example, to paginate posts on a hypothetical blog page you could use something like this:
{% autopaginate posts pagesize %}
{% paginate using "pagination/blog/post.html" %}
The default pagination template is contained in the pagination/pagination.html file inside the distribution. You could extend it and only customize the parts you care about. Please inspect the template to see the blocks it defines that you could customize.
You can use autopaginate/paginate multiple times in the same template. The only requirement is to call autopaginate before calling paginate. That is, paginate acts on the most recent call to autopaginate.
It is important, when using linaro-django-pagination in conjunction with file uploads, to be aware of when request.page is accessed. As soon as request.page is accessed, request.upload_handlers is frozen and cannot be altered in any way. It’s a good idea to access the page attribute on the request object as late as possible in your views.
In linaro-django-pagination, there are no required settings. There are, however, a small set of optional settings useful for changing the default behavior of the pagination tags. Here’s an overview:
The number of orphans allowed. According to the Django documentation, orphans are defined as:
The minimum number of items allowed on the last page, defaults to zero.