Club Drupal

 *       'title' => t('Node'),

 *       'help' => t('Display the node with standard node view.'),

 *       'handler' => 'views_plugin_row_node_view',

 *       'theme' => 'views_view_row_node',

 *       'uses options' => TRUE,

 *       'type' => 'normal',

 *     ),

/**

 * Describes data tables (or the equivalent) to Views.

 *

 *

 *   An associative array describing the data structure. Primary key is the

 *   name used internally by Views for the table(s) – usually the actual table

 *   name. The values for the key entries are described in detail below.

  // table:

  //

  // CREATE TABLE example_table (

  //   plain_text_field VARCHAR(32) COMMENT 'Just a plain text field.',

  //   PRIMARY KEY(nid)

  // );

  // First, the entry $data['example_table']['table'] describes properties of

  // the actual table – not its content.

  // The 'group' index will be used as a prefix in the UI for any of this

  // table's fields, sort criteria, etc. so it's easy to tell where they came

  // from.

  // is not very useful for this table, as it isn't really a distinct object of

  // its own, but it makes a good example.

  $data['example_table']['table']['base'] = array(

    'title' => t('Example table'),

    'help' => t('Example table contains example content and can be related to nodes.'),

    'weight' => -10,

  // table, the fields are automatically available.

  $data['example_table']['table']['join'] = array(

    // Index this array by the table name to which this table refers.

    'node' => array(

      'left_field' => 'nid',

      'field' => 'nid',

    ),

  );

  //     footer or as no result behaviour.

  //

  // The handler descriptions are described with examples below.

  // Node ID table field.

  $data['example_table']['nid'] = array(

    'title' => t('Example content'),

    // other direction, use hook_views_data_alter(), or use the 'implicit' join

    // method described above.

    'relationship' => array(

      // 'field' => 'nid' -- see hook_views_data_alter(); not needed here.

      'handler' => 'views_handler_relationship',

      'label' => t('Default label for the relationship'),

    'help' => t('Just a plain text field.'),

    'field' => array(

      'handler' => 'views_handler_field',

    ),

    'sort' => array(

      'handler' => 'views_handler_sort',

    'field' => array(

      'handler' => 'views_handler_field_numeric',

      'click sortable' => TRUE,

    'filter' => array(

      'handler' => 'views_handler_filter_numeric',

    ),

    ),

    'filter' => array(

      'handler' => 'views_handler_filter_boolean_operator',

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

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

      'type' => 'yes-no',

 * 'path' key returned by MODULENAME_views_api(), or the same directory as the

 * .module file, if 'path' is unspecified.

 *

 *   An array of all Views data, passed by reference. See hook_views_data() for

 *   structure.

 *

    'title' => t('Example relationship'),

    'help' => t('Example help'),

    'relationship' => array(

      'handler' => 'views_handler_relationship',

      'label' => t('Default label for relationship'),

      'title' => t('Title seen when adding relationship'),

/**

 * Override the default data for a Field API field.

 *

 * field in the module that defines the field type (as declared in the field

 * array). It is not invoked in other modules.

 *

 * If no hook implementation exists, hook_views_data() falls back to

 * field_views_field_default_views_data().

 *

 * @see field_views_data()

 * @see hook_field_views_data_alter()

 * @see hook_field_views_data_views_data_alter()

 */

function hook_field_views_data($field) {

}

/**

 * the field, and therefore may be used to alter the default data that

 * field_views_field_default_views_data() supplies for the field.

 *

 *

 * @see field_views_data()

 * @see hook_field_views_data()

/**

 * Alter the views data on a per field basis.

 *

 * each field in the module that defines the field type (as declared in the

 * field array). It is not invoked in other modules.

 *

 * .module file, if 'path' is unspecified. All plugin files need to be

 * referenced in MODULENAME.info with the files[] directive.

 *

 *   An array on the form $plugins['PLUGIN TYPE']['PLUGIN NAME']. The plugin

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

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

 *       selectable in the ui, though on the api side they still exists.

 *     - uses options: Set to TRUE to denote that the plugin has an additional

 *       options form.

 *     - help topic: The name of an entry by advanced help for the plugin.

 *     - theme: The name of a theme suggestion to use for the display.

 *     - js: An array with paths to js files that should be included for the

 *       should be added. Can for example be 'page' or 'block'. If you don't

 *       specify it there will be contextual links around the rendered view. If

 *       this is not set or regions have been specified, views will display an

 *     - uses hook menu: Set to TRUE to have the display included by

 *       views_menu_alter(). views_menu_alter executes then execute_hook_menu

 *       on the display object.

 *     - uses fields: Set to TRUE to have the style plugin accept field

 *       handlers.

 *     - uses grouping: Set to TRUE to allow the grouping settings for rows.

 *

 *   - Used by row plugins:

 *     - uses fields: Set to TRUE to have the row plugin accept field handlers.

  );

  return array(

    'argument validator' => array(

      'taxonomy_term' => array(

        'title' => t('Taxonomy term'),

        'handler' => 'views_plugin_argument_validate_taxonomy_term',

      ),

    ),

    'argument default' => array(

  $plugins['row']['node']['base'][] = 'apachesolr';

}

/**

 * Register View API information.

 *

 * This is required for your module to have its include files loaded; for

 * example, when implementing hook_views_default_views().

 *

 *   An array with the following possible keys:

 *   - api: (required) The version of the Views API the module implements.

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

}

/**

 *

 * This hook should be placed in MODULENAME.views_default.inc and it will be

 * auto-loaded. MODULENAME.views_default.inc must be in the directory specified

 * The $view->disabled boolean flag indicates whether the View should be

 * enabled (FALSE) or disabled (TRUE) by default.

 *

 *   An associative array containing the structures of views, as generated from

 *   the Export tab, keyed by the view name. A best practice is to go through

 *   and add t() to all title and label strings, with the exception of menu

 */

function hook_views_default_views() {

  // Begin copy and paste of output from the Export tab of a view.

  $view->name = 'frontpage';

  $view->description = 'Emulates the default Drupal front page; you may set the default home page path to this view to make it your front page.';

  $view->tag = 'default';

  $handler->display->display_options['sitename_title'] = '1';

  // (Export ends here.)

  // Add view to list of views to provide.

  $views[$view->name] = $view;

  return $views;

}

/**

 * Performs replacements in the query before being performed.

 *

 *   The View being executed.

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

 *   to replace them with. The strings to replace are often surrounded with

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

}

/**

 *

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

 *   to replace them with.

 */

}

/**

 *

 * Adding output to the view can be accomplished by placing text on

 * $view->attachment_before and $view->attachment_after.

 *   The view object about to be processed.

 *   The machine name of the active display.

 *   An array of arguments passed into the view.

 */

  // Change the display if the acting user has 'administer site configuration'

  // permission, to display something radically different.

  // (Note that this is not necessarily the best way to solve that task. Feel

  // free to contribute another example!)

  if (

  ) {

    $view->set_display('private_display');

  }

}

/**

 *

 * Adding output to the view can be accomplished by placing text on

 * $view->attachment_before and $view->attachment_after.

 *   The view object about to be processed.

 */

function hook_views_pre_build(&$view) {

}

/**

 *

 * Adding output to the view can be accomplished by placing text on

 * $view->attachment_before and $view->attachment_after.

 *   The view object about to be processed.

 */

function hook_views_post_build(&$view) {

}

/**

 *

 * Adding output to the view can be accomplished by placing text on

 * $view->attachment_before and $view->attachment_after.

 *   The view object about to be processed.

 */

function hook_views_pre_execute(&$view) {

}

/**

 *

 * Adding output to the view can be accomplished by placing text on

 *   The view object about to be processed.

 */

function hook_views_post_execute(&$view) {

}

/**

 *

 * Adding output to the view can be accomplished by placing text on

 * $view->attachment_before and $view->attachment_after. Altering the content

 * can be achieved by editing the items of $view->result.

 *

 * This hook can be utilized by themes.

 *   The view object about to be processed.

 */

function hook_views_pre_render(&$view) {

 * so all ids used in the query should be discoverable.

 *

 * This hook can be utilized by themes.

 *   The view object about to be processed.

 *   A flat string with the rendered output of the view.

 *   The cache settings.

 */

function hook_views_post_render(&$view, &$output, &$cache) {

 * 'path' key returned by MODULENAME_views_api(), or the same directory as the

 * .module file, if 'path' is unspecified.

 *

 *   The view object about to be processed.

 *   An object describing the query.

 * @see hook_views_query_substitutions()

 */

function hook_views_query_alter(&$view, &$query) {

}

/**

 *

 * This hook should be placed in MODULENAME.views.inc and it will be

 * auto-loaded. MODULENAME.views.inc must be in the directory specified by the

 * Warning: $view is not a reference in PHP4 and cannot be modified here. But it

 * IS a reference in PHP5, and can be modified. Please be careful with it.

 *

 *   An associative array with two keys:

 *   - query: An array of rows suitable for theme('table'), containing

 *     information about the query and the display title and path.

 *   - statistics: An array of rows suitable for theme('table'), containing

 *     performance statistics.

 *   The view object.

 * @see theme_table()

 */

function hook_views_preview_info_alter(&$rows, $view) {

}

/**

 *

 *   An array of links which will be displayed at the top of the view edit form.

 *   Each entry should be on a form suitable for theme('link').

 *   The full view object which is currently edited.

 *   The current display id which is edited. For example that's 'default' or

 *   'page_1'.

 */

}

/**

 *

 *   The view which is requested.

 */

function hook_views_ajax_data_alter(&$commands, $view) {