AsciiDoc filter

You can find documentation on the README included in the project.
Here the compiled versions: 6.x-1.x - 7.x-1.x

Better Exposed Filter Options

This page outlines the various exposed form options available when using the Better Exposed Filters module.

There are several supported versions of Drupal, Views, and BEF. In general, Drupal 6.x versions of BEF are not open to new features unless a request is accompanied by a patch. Most new development is taking place in the Drupal 7.x branch.

Most BEF features are available with filters that have a limited number of options. In general an open-ended filter, such as a publication date, cannot be tweaked by BEF. There is work in the 7.x branch to add jQuery UI widgets for some of these fields (e.g.: a date-picker for publication date fields) to make date entry easier, however that functionality will not be backported to 6.x because of the lack of jQuery UI components in core.

Contextual filters and paths

The normal way a view gets values for contextual filters is by the view path. The easiest way of doing this is to append filter values to the path, separated by slashes. It is also possible to have contextual filter values within a path. This is done by using a percent sign where the view expects a contextual filter value in the path of the view (for example user/%/comments).

Having contextual filter values inside paths is particularly useful when creating menu tabs, which is the subject of the next section.

Configuring contextual filters

Contextual filters are added and managed in the advanced section in the Views main configuration panel. They generally follow the same patterns as filters, but have a number of settings that normal filters lack. (See figure 10.7) Take a deep breath:

  • When the filter value is not in the URL: This setting determines the view behavior, if there is no value for the contextual filter. This is an essential setting when using contextual filters in block displays.
  • Override title: This setting is used to alter the view's title, if there is a contextual filter value present. You may use variables in the form %1, %2, and so on, to include the first, or second filter values in the title (and so on). If there is any title element associated with the filter value, such as a node title for node IDs or user names for user IDs, the title element will be used - but only if the contextual filter is validated (see "Specify validation criteria" below). A typical use case is the title articles written by %1.
  • Override breadcrumb: This setting allows you to set the breadcrumb to use when a filter value is present – or default to using the view title. The breadcrumb will lead to the view without this contextual filter value and the view must have a valid response to this.

Contextual filters

Views is a highly flexible module to start with, but the contextual filters increase the use cases for the module by an order of magnitude. Contextual filters work similarly to regular filters, but there is one important difference. Instead of setting a filter value manually, the value is fetched from variables sent programmatically to the view. A regular filter could give you all nodes written by a specified user. A contextual filter for a node author would be able to display all nodes written by the currently viewed user, or the same user who wrote the currently viewed node. The concept is that contextual filters prepare a view for filtering, but the filter value is not yet determined. When the view is eventually called, it is also provided with data used to complete the contextual filters.

The classic example of how contextual filter values are provided to views is by the view path. If a view has the path example.com/my-view, the URL example.com/my-view/story/22 will call the view along with two values for contextual filters (in this case story and 22). But there are more ways of providing contextual filter values. These are discussed in Chapter about Page manager and Panels.

Google Books Module and API Usage

Google Books Module

Author: Darrell Ulm

The Google Books module is a filter and a Google Books API that allows a user to insert rich Google book data into nodes via filters.

Pages

Subscribe with RSS Subscribe to RSS - filters