Contains filters are case sensitve
Namesort descending Description
About Views handlers In Views, a handler is an object that is part of the view and is part of the query building flow.
About Views plugins In Views, a plugin is a bit like a handler, but plugins are not directly responsible for building the query. Instead, they are objects that are used to display the view or make other modifications.
CRUD functions for export. supports a small number of CRUD functions that should always work for every exportable object, no matter how complicated. These functions allow complex objects to provide their own callbacks, but in most cases, the default callbacks will be…
Export alterations
Feature module hooks Hooks invoked on Feature modules when that module is enabled, disabled, rebuilt, or reverted. These are ONLY invoked on the Features module on which these actions are taken.
Feature's component alter hooks Hooks to modify components defined by other features. These come in the form hook_COMPONENT_alter where COMPONENT is the default_hook declared by any of components within features.
Feeds Tamper API API functions for dealing with plugins and plugin instances.
Field implementations
Funtions for loading libraries
Hook and callback implementations
Import and clear hooks
Mapping API
Objects that represent a View or part of a view These objects are the core of Views do the bulk of the direction and storing of data. All database activity is in these objects.
Pathauto: Automatically generates aliases for content The Pathauto module automatically generates path aliases for various kinds of content (nodes, categories, users) without requiring the user to manually specify the path alias. This allows you to get aliases like /category/my-node-title.html instead of…
Plugin API Feeds offers a CTools based plugin API. Fetchers, parsers and processors are declared to Feeds as plugins.
Propery implementations
Sample Webform Component In each of these examples, the word "component" should be replaced with the, name of the component type (such as textfield or select). These are not actual hooks, but instead samples of how Webform integrates with its own built-in components.
The life of a view This page explains the basic cycle of a view and what processes happen.
Utility functions
UUID implementation of Entity API
UUID support for Entity API Functions that extends the Entity API with UUID support.
Views access plugins @todo.
Views AJAX library Handles the server side AJAX interactions of Views.
Views area handlers Handlers to tell Views what can display in header, footer and empty text in a view.
Views argument default plugins Allow specialized methods of filling in arguments when they aren't provided.
Views argument handlers Handlers to tell Views how to contextually filter queries.
Views argument validate plugins Allow specialized methods of validating arguments.
Views cache plugins @todo.
Views display plugins Display plugins control how Views interact with the rest of Drupal.
Views exposed form plugins Plugins that handle the validation/submission and rendering of exposed forms.
Views field handlers Handlers to tell Views how to build and display fields.
Views filter handlers Handlers to tell Views how to filter queries.
Views hooks Hooks that can be implemented by other modules in order to implement the Views API.
Views join handlers Handlers to tell Views how to join tables together.
Views localization plugins @todo.
Views module handlers Handlers exposed by various modules to Views.
Views pager plugins @todo.
Views query plugins A Views query plugin builds SQL to execute using the Drupal database API.
Views relationship handlers Handlers to tell Views how to create alternate relationships.
Views row plugins Row plugins control how Views outputs an individual record.
Views sort handlers Handlers to tell Views how to sort queries.
Views style plugins Style plugins control how a view is rendered. For example, they can choose to display a collection of fields, node_view() output, table output, or any kind of crazy output they want.
Views template files All views templates can be overridden with a variety of names, using the view, the display ID of the view, the display type of the view, or some combination thereof.
Webform Module Hooks Webform's hooks enable other modules to intercept events within Webform, such as the completion of a submission or adding validation. Webform's hooks also allow other modules to provide additional components for use within forms.
Wysiwyg API @todo Forked from Panels; abstract into a separate API module that allows contrib modules to define supported include/plugin types.

Other projects