Package: django-bootstrap-pagination-forked
Project No Longer MaintainedWARNING: This is fork of the jmcclell's repo for Django 4.0 compatibility. I'll try to live this package with your supportThis project lived a long and useful life, but it's been inactive for quite some time and I believe its relevancy has faded.It will remain here on Github in a read-only, archived state but there will be no more updates.Django Bootstrap PaginationBootstrap CompatibilityVersionsBootstrap VersionsNotes< 1.1.02.x> 1.1.0, < 1.7.03.x>= 1.7.03.x, 4.xbootstrap_pager is only compatible with Bootstrap  3.xThis application serves to make using Twitter's Bootstrap Pagination styles
work seamlessly with Django Page objects. By passing in a Page object and
one or more optional arguments, Bootstrap pagination bars and pagers can
be rendered with very little effort.Compatible with Django1.2+InstallationPIPThis will install the latest stable release from PyPi.pip install django-bootstrap-paginationDownloadDownload the latest stable distribution from:http://pypi.python.org/pypi/django-bootstrap-paginationDownload the latest development version from:github @http://www.github.com/jmcclell/django-bootstrap-paginationsetup.py installUsageSetupMake sure you include bootstrap_pagination in your installed_apps list in settings.py:INSTALLED_APPS = (
        'bootstrap_pagination',
    )Additionally, include the following snippet at the top of any template that makes use of
the pagination tags:{% load bootstrap_pagination %}Finally, make sure that you have the request context processor enabled:# Django 1.8+
    TEMPLATES = [
        {
            # ...
            'OPTIONS': {
                context_processors': [
                    # ...
                    'django.template.context_processors.request',
                ]
            }
        }
    ]

    # Django < 1.8
    TEMPLATE_CONTEXT_PROCESSORS = {
        "django.core.context_processors.request",
    )bootstrap_paginateAll Optional Argumentsrange- Defines the maximum number of page links to showshow_prev_next- Boolean. Defines whether or not to show the Previous and Next
links. (Accepts"true"or"false")previous_label- The label to use for the Previous linknext_label- The label to use for the Next linkshow_first_last- Boolean. Defines whether or not to show the First and Last links.
(Accepts"true"or"false")first_label- The label to use for the First page linklast_label- The label to use for the Last page linkshow_index_range- Boolean, defaults to "false". If "true" shows index range of items instead of page numbers in the paginator. For example, if paginator is configured for 50 items per page, show_index_range="true" will display [1-50, 51-100,101-150, 151-200, 201-250, etc.] rather than [1, 2,3, 4, 5, etc.].url_view_name- A named URL reference (such as one that might get passed into the URL
template tag) to use as the URL template. Must be resolvable by thereverse()function.If this option is not specified, the tag simply
uses a relative url such as?page=1which is fine in most situationsurl_param_name- Determines the name of theGETparameter for the page number. The
default is"page". If nourl_view_nameis defined, this string
is appended to the url as?{{url_param_name}}=1.url_extra_args-Only valid when url_view_name is set.Additional arguments to
pass intoreverse()to resolve the URL.url_extra_kwargs-Only valid whenurl_view_nameis set.Additional named
arguments to pass intoreverse()to resolve the URL. Additionally,
the template tag will add an extra parameter to this for the
page, as it is assumed that if given a url_name, the page will
be a named variable in the URL regular expression. In this case,
theurl_param_namecontinues to be the string used to represent
the name. That is, by default,url_param_nameis equal topageand thus it is expected that there is a namedpageargument in the
URL referenced byurl_view_name. This allows us to use pretty
pagination URLs such as/page/1extra_pagination_classes- A space separated list of CSS class names that
will be added to the top level<ul>HTML element.
In particular, this can be utilized in Bootstrap 4
installations to add the appropriate alignment
classes from Flexbox utilities: eg:justify-content-centerBasic UsageThe following will show a pagination bar with a link to every page, a previous link, and a next link:{% bootstrap_paginate page_obj %}The following will show a pagination bar with at most 10 page links, a previous link, and a next link:{% bootstrap_paginate page_obj range=10 %}The following will show a pagination bar with at most 10 page links, a first page link, and a last page link:{% bootstrap_paginate page_obj range=10 show_prev_next="false" show_first_last="true" %}Advanced UsageGiven a url configured such as:archive_index_view=ArchiveIndexView.as_view(date_field='date',paginate_by=10,allow_empty=True,queryset=MyModel.all(),template_name='example/archive.html')urlpatterns=patterns('example.views',url(r'^$',archive_index_view,name='archive_index'),url(r'^page/(?P<page>\d+)/$',archive_index_view,name='archive_index_paginated'))We could simply use the basic usage (appending ?page=#) with thearchive_indexURL above,
as thearchive_index_viewclass based generic view from django doesn't care how it gets
the page parameter. However, if we want pretty URLs, such as those defined in thearchive_index_paginatedURL (ie: /page/1), we need to define the URL in our template tag:{% bootstrap_paginate page_obj url_view_name="archive_index_paginated" %}Because we are using a default page parameter name of "page" and our URL requires no other
parameters, everything works as expected. If our URL required additional parameters, we
would pass them in using the optional argumentsurl_extra_argsandurl_extra_kwargs.
Likewise, if our page parameter had a different name, we would pass in a differenturl_param_nameargument to the template tag.bootstrap_pagerA much simpler implementation of the Bootstrap Pagination functionality is the Pager, which
simply provides a Previous and Next link.All Optional Argumentsprevious_label- Defines the label for the Previous linknext_label- Defines the label for the Next linkprevious_title- Defines the link title for the previous linknext_title- Defines the link title for the next linkcentered- Boolean. Defines whether or not the links are centered. Defaults to false.
(Accepts "true" or "false")url_view_name- A named URL reference (such as one that might get passed into the URL
template tag) to use as the URL template. Must be resolvable by thereverse()function.If this option is not specified, the tag simply
uses a relative url such as?page=1which is fine in most situationsurl_param_name- Determines the name of theGETparameter for the page number. Th
default is"page". If nourl_view_nameis defined, this string
is appended to the url as?{{url_param_name}}=1.url_extra_args-Only valid whenurl_view_nameis set.Additional arguments to
pass intoreverse()to resolve the URL.url_extra_kwargs-Only valid whenurl_view_nameis set.Additional named
arguments to pass intoreverse()to resolve the URL. Additionally,
the template tag will add an extra parameter to this for the
page, as it is assumed that if given a url_name, the page will
be a named variable in the URL regular expression. In this case,
theurl_param_namecontinues to be the string used to represent
the name. That is, by default,url_param_nameis equal to"page"and thus it is expected that there is a namedpageargument in the
URL referenced byurl_view_name. This allows us to use pretty
pagination URLs such as/page/1url_anchor- The anchor to use in URLs. Defaults toNoneextra_pager_classes- A space separated list of CSS class names that will be added
to the top level<ul>HTML element. This could be used to, as an
example, add a class  to prevent the pager from showing up when
printing.UsageUsage is basically the same as for bootstrap_paginate. The simplest usage is:{% bootstrap_pager page_obj %}A somewhat more advanced usage might look like:{% bootstrap_pager page_obj previous_label="Newer Posts" next_label="Older Posts" url_view_name="post_archive_paginated" %}