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. |
Actions |
Functions that perform an action on a certain system object. |
Ajax framework |
Functions for Backdrop's Ajax framework. |
Ajax framework commands |
Functions to create various Ajax commands. |
Authorized operations |
Functions to run operations with elevated privileges via authorize.php. |
Batch operations |
Creates and processes batch operations. |
Block Caching |
Constants that define each block's caching state. |
Callbacks |
Callback function signatures. |
Content markers |
Markers used by theme_mark() and node_mark() to designate content. |
Database abstraction layer |
Allow the use of different database servers using the same code base. |
Default theme implementations |
Functions and templates for the user interface to be implemented by themes. |
DifferenceEngine |
A PHP diff engine for phpwiki. (Taken from phpwiki-1.3.3) |
Drupal compatibility layer. |
These functions and classes are wrappers around Backdrop functions that allow
for Drupal 7 modules to work with Backdrop. All of these functions are made
available if the "backdrop_drupal_compatibility" option is enabled in your
site's… |
Field API |
Attach custom data fields to Backdrop entities. |
Field API bulk data deletion |
Clean up after Field API bulk deletion operations. |
Field Attach API |
Operate on Field API data attached to Backdrop entities. |
Field CRUD API |
Create, update, and delete Field API fields, bundles, and instances. |
Field Formatter API |
Define Field API formatter types. |
Field Info API |
Obtain information about Field API configuration. |
Field Language API |
Handling of multilingual fields. |
Field Storage API |
Implement a storage engine for Field API data. |
Field Types API |
Define field types. |
Field Widget API |
Define Field API widget types. |
File access rights |
The file access system determines who can do what to which files. |
File displays API |
Functions to load and save information about file displays. |
File interface |
Common file handling functions. |
File module public API functions |
These functions may be used to determine if and where a file is in use. |
Formatting |
Functions to format numbers, strings, dates, etc. |
Form builder functions |
Functions that build an abstract representation of a HTML form. |
Form generation |
Functions to enable the processing and display of HTML forms. |
Hook implementations for user-created content types |
Functions that implement hooks for user-created content types. |
Hooks |
Allow modules to interact with the Backdrop core. |
HTTP handling |
Functions to properly handle HTTP responses. |
Image toolkits |
Functions for image file manipulations. |
Input validation |
Functions to validate user input. |
Installer module: file management |
Installer module file management functions. |
Installer module: install |
Installer module functionality for installing new code. |
Installer module: update |
Installer module functionality for updating existing code. |
Language Negotiation API functionality |
Functions to customize the language types and the negotiation process. |
Language negotiation options |
Functions for language negotiation. |
Locking mechanisms |
Functions to coordinate long-running operations across requests. |
Logging severity levels |
Logging severity levels as defined in RFC 3164. |
Menu context types |
Flags for use in the "context" attribute of menu router items. |
Menu flags |
Flags for use in the "type" attribute of menu items. |
Menu item types |
Definitions for various menu item types. |
Menu status codes |
Status codes for menu callbacks. |
Menu system |
Define the navigation menus, and route page requests to code based on URLs. |
Menu tree parameters |
Parameters for a menu tree. |
Node access rights |
The node access system determines who can do what to which nodes. |