Club Drupal

 * responsible for building the query. Instead, they are objects that are used

 * to display the view or make other modifications.

 *

 * - Display: Display plugins are responsible for controlling *where* a view

 *   lives; that is, how they are being exposed to other parts of Drupal. Page

 *   and block are the most common displays, as well as the ubiquitous 'master'

      'label' => t('Published'),

      // This setting is used by the boolean filter handler, as possible option.

      'type' => 'yes-no',

      'use equal' => TRUE,

    ),

    'sort' => array(

 *   must be one of row, display, display_extender, style, argument default,

 *   argument validator, access, query, cache, pager, exposed_form or

 *   localization. The plugin name should be prefixed with your module name.

 *   following entries:

 *   - Used by all plugin types:

 *     - title (required): The name of the plugin, as shown in Views. Wrap in

 *   - path: (optional) If includes are stored somewhere other than within the

 *     root module directory, specify its path here.

 *   - template path: (optional) A path where the module has stored it's views

 *     uses the template files for the views. You can use the same naming

 *     conventions like for normal views template files.

 */

 *   The View being executed.

 * @return

 *   An array with keys being the strings to replace, and the values the strings

 *   '***', as illustrated in the example implementation.

 */

function hook_views_query_substitutions($view) {

 *   The view object about to be processed.

 */

function hook_views_pre_build(&$view) {

  // attachments from all views on Mondays.

  // (This alter could be done later in the execution process as well.)

  if (date('D') == 'Mon') {

  // Replace Views' method for scrolling to the top of the element with your

  // custom scrolling method.

  foreach ($commands as &$command) {

    }

  }

}