Group items tagged

The Drupal 7 Database API provides a standard, vendor-agnostic abstraction layer for accessing database servers. The API is designed to preserve the syntax and power of SQL as much as possible, but also: - to support multiple database servers easily;- to allow developers to leverage more complex functionality, such as transactions;- to provide a structured interface for the dynamic construction of queries;- to enforce security checks and other good practices;- to provide modules with a clean interface for intercepting and modifying a site's queries. The main Database API documentation is derived directly from comments in the code. This Handbook section augments those API docs by providing a tutorial for module authors who wish to interact with the database system, as well as an overview of the system from an administrator's point of view. Note that this Handbook may not cover every feature of the API. The Database API was built with object-oriented design concepts, and this document therefore assumes at least a partial familiarity with those concepts. However, most common operations have a procedural front-end as well, and developers may choose to use the procedural style for more readable code.

Using Display Suite to create custom teaser displays.

In order to make a private download truly private, you need to move the files directory (usually under sites/default/files) into a new place outside the Drupal installation. It should be in a place the user can't access via browser.

Information on Varnish Grace and Saint modes. "A key feature of Varnish is its ability to shield you from misbehaving web- and application servers."