Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Views infinite scroll allows you to load and display pages of any view inline, using AJAX (this has been called infinite scrolling, load more, autopaging, endless pages and more). The pager can be triggered with the press of a button or automatically as the user scrolls to the bottom of the view's content.
The Drupal 8 version of Views Infinite Scroll is a lightweight solution which:
Flippy is an ultra-simple module that generates previous/next pagers for content types. On the Node type administration screen, you can turn Flippy on or off
for each content type. It'll generate a unique pager for each content type, so you can page through Articles or page through Blog posts, but you can't page
through all nodes on the site.
To change the position of the pager, visit the content type's Manage Display page, where fields and other fieldish things can be dragged about. Flippy's there, too.
In an effort to minimize the duplication of jcarousel based modules this module is being deprecated for the Drupal 6 version onward and is being replaced by the jcarousel module. As of the Drupal 6 2.x branch of the jcarousel module views integration is provided.
The carousel module, jcarousel module, and this module are being merged into one effort with the maintainers combining efforts in one module.
Break long pages into smaller ones automatically by words(or characters) limit, or by means of a customizable pagination tag:
First page here.
Second page here.
More pages here.
Drupal 7 version
Not all of the features introduced in the Drupal 6 version of paging are supported in Drupal 7. If you need a feature that is no longer supported, please search the issue queue, at right, for a similar request, and state your case. Features that are still needed may be added back in.
Upgrading from D6 to D7
We are currently working on an upgrade path from D6 to D7.
Clean Pagination is a very simple module that allows you to enable clean URL pagination for specified pages. The way Drupal typically works, if you had a view with the URL 'my-view', subsequent pages would normally use a query to pass the page number, as in 'my-view?page=2'. When Clean Pagination is being used for a page, it will create a url like 'my-view/2'.
Currently, the module has just two settings: 1) Set the pages where you want clean pagination enabled, and 2) Enable search-engine-friendly pagination hyperlinks.
A note on performance: Free Pager iterates through all view results, to find a match on the current URL. If your Free Pager views have a lot of results (say 100+), this will have serious effects on page load times. It can partly be helped by standard Views caching, but not completely.
Free Pager has just got a new co-maintainer, so hopefully the performance issues can be solved soon.
Quick comparison: Free pager is (afaik) the only Drupal module that allows putting pagers on basically anything – not only content. If you want to paginate content, compare with other modules.
This module allows you to use Views to create simple forward/next pagers. It
provides a new display, Pager block, which will create a block with pager for
items listed in the view.
This pager module is a bit more difficult to wrap your head around than most
pager modules. In return, you get much more flexibility in what you can put
pagers on, and how the pagers should work. The basic concept is this:
This module adds next and previous links on content pages when accessed from a view. It is intended for dynamic and/or paged view results, where the result set changes according to exposed filters, current user access rights,...
You may need this module if the content which comes after a given content depends on context, and more precisely depends on which content list you came from. This means no navigation link will be displayed if you come to the second level page directly, without using the first level view.
Pagination (Node) allows the main content of arbitrary node types (Page, Story, etc...) to be paginated according to one of three methods:
Method 1: Content is paginated by a selectable "words per page" count. Method 2: Content is paginated by manual breaks, inserted by the content creator. Method 3: Content is paginated by manual breaks, based on <h3> tags.
Method 1 allows for quick and easy pagination, and is ideal for users who are looking to have their longer content split into multiple pages with the least amount of hassle. Just select the "words per page" threshold for a particular content type, and all existing and future nodes of that type will be automatically paginated accordingly.
Methods 2 and 3 allow for fine-tuned control over pagination breaks, useful for content creators who need to set specific break points in their content. Method 2 paginates content based on the presence of break tags ([pagebreak] or [ header = SOME TITLE ]), whereas Method 3 paginates based on <h3> elements.
note: To use Method 3 pagination, make sure <h3> tags are allowed under your Input Filters.
1- A special kind of layout to glossary view(which is available by default with views) or any view, see in screenshot.
2- Providing pager with selectbox and textbox.
3-A default view is added for example.
4- Making items per pager independent of expose form submit.(A usability improvement).
Go to module configuration and enter view machine names separated by comma. See the layout on view.
PageFlip simulates "flipping through the pages" of books, magazines, comics, flyers, or other "book"-like content.
This module implements "infinite pager" (earlier called "sliding pager") functionality for Views. Infinite pagers open the next page via Ajax below the current page, each sub-page expanding the page vertically downwards. (For a well-known infinite pager example, visit a stream on Twitter.com).
Enable jQuery 1.7 (or higher) in jQuery Update settings ("admin/config/development/jquery_update"). Notice: In our tests 1.7 worked with fewest problems. 1.8 and others are also possible. BUT: Please check if there are bad side effects in your environment!
Thanks to the following projects that were utilitized:
A block with direct links to Field Group's Multipage pages.
This module extends the functionality of Field Group's Multipage format type for entities by providing a block that allows you to access all multipages directly from a list.
By default you only have Previous page and Next page buttons to navigate with, but for large and complex forms this may be too restrictive, say when you need to edit a minor detail on page 8 in a 12 page application form.