Paging

Watch the video demo

Q-Views is currently in Alpha and has a couple of security flaws that need to be sorted out before being released as beta. Note that Alpha releases should never be used on production sites. Please also note this module has multiple critical security flaws.

Query-Based Views (Q-Views) provides the Views-like functionality of generating reports or content feeds, but starts the process with a raw SQL query. In Views, the query is constructed through setting up configuration, but in Q-Views you supply the query directly. This can be a more rapid, reasonable solution in some situations. Q-Views is very AJAX-y by default, with ajax-based pagination and searching, which also means rapid browsing through data. Views is much more mature, so it's encouraged that you use Views when you can, but Q-Views can provide a lot of functionality with low configuration overhead when you would normally build a feed or report outside of Views.

This module themes the pager with a textfield input for direct random access to any page instead of clicking page links. It's especially useful when the number of pages are very large. Drupal's built-in pager only allows sequential access to page and it could take forever to scroll through very large number of pages. This pager is very compact and can be made super mini by CSS styling the first/previous/next/last links with graphics like the example shown here.

This pager can be used in two ways:

1. Through the module settings page, admin can replace the default built-in pager or Views' views_mini_pager with this pager.

2. Developers can use the 'drpager' theme hook. Instead of calling:

Pager preference allows users to set the number of results to display in a paginated page throughout the site.

A new div element will be displayed below the pager to allow users to set their pagination preference simply as:

Show 25 / 50 / 100

pager.inc patch
---------------
Requires patch to pager.inc file located in /YOUR_SITE/includes/ folder to allow for user's pager preference to override result set limit. Run pager.inc.patch against pager.inc.

*** NOTE: No activity recently, so V7 is going to first release. Please run 'update.php'! It works in a minimal way with Sitemap and Nice Menus. Hurrah! Read about it here.

V6.x. seems stable, so now moved to recommended. No need to upgrade from 5.x unless you want the new features. You can preserve your data - read about that here.

Drupal Versioning go here.
***

Intro
Makes custom menus from selected branches of a taxonomy.

People keep asking for this. They keep getting told that it's not possible, it's not Drupal, and "who would want it anyway?" For all you impossible people out there, here is Taxonomy Treemenu.

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.

Pager display

*** NOTE: You've seen that V4 is out? Please read the message in issues. ***

Taxonomy Router pages Taxonomy vocabularies/terms (the module treats them as very similar items) as a list of terms or nodes.

This kind of functionality keeps appearing in taxonomy modules. So now it is a separate module which may, for code minimalists, prove useful in itself.