diff --git a/developer/hooks/core.php b/developer/hooks/core.php index 8a281b0..5e569d6 100755 --- a/developer/hooks/core.php +++ b/developer/hooks/core.php @@ -2053,34 +2053,32 @@ function hook_taxonomy($op, $type, $array = NULL) { /** * Register a module (or theme's) theme implementations. * - * Modules and themes implementing this return an array of arrays. The key + * Modules and themes implementing this hook return an array of arrays. The key * to each sub-array is the internal name of the hook, and the array contains - * info about the hook. Each array may contain the following items: + * information about the hook. Each array may contain the following elements: * * - arguments: (required) An array of arguments that this theme hook uses. This - * value allows the theme layer to properly utilize templates. The - * array keys represent the name of the variable, and the value will be - * used as the default value if not specified to the theme() function. - * These arguments must be in the same order that they will be given to - * the theme() function. + * value allows the theme layer to properly utilize templates. The array keys + * represent the name of the variable, and the value will be used as the + * default value if not specified to the theme() function. These arguments + * must be in the same order that they will be given to the theme() function. * - file: The file the implementation resides in. This file will be included * prior to the theme being rendered, to make sure that the function or * preprocess function (as needed) is actually loaded; this makes it possible * to split theme functions out into separate files quite easily. * - path: Override the path of the file to be used. Ordinarily the module or * theme path will be used, but if the file will not be in the default path, - * include it here. This path should be relative to the Drupal root - * directory. + * include it here. This path should be relative to the Drupal root directory. * - template: If specified, this theme implementation is a template, and this - * is the template file without an extension. Do not put .tpl.php - * on this file; that extension will be added automatically by the default - * rendering engine (which is PHPTemplate). If 'path', above, is specified, - * the template should also be in this path. + * is the template file without an extension. Do not put .tpl.php on this + * file; that extension will be added automatically by the default rendering + * engine (which is PHPTemplate). If 'path', above, is specified, the template + * should also be in this path. * - function: If specified, this will be the function name to invoke for this - * implementation. If neither file nor function is specified, a default - * function name will be assumed. For example, if a module registers - * the 'node' theme hook, 'theme_node' will be assigned to its function. - * If the chameleon theme registers the node hook, it will be assigned + * implementation. If neither 'template' nor 'function' is specified, a + * default function name will be assumed. For example, if a module registers + * the 'node' theme hook, 'theme_node' will be assigned to its function. If + * the chameleon theme registers the node hook, it will be assigned * 'chameleon_node' as its function. * - pattern: A regular expression pattern to be used to allow this theme * implementation to have a dynamic name. The convention is to use __ to @@ -2090,19 +2088,18 @@ function hook_taxonomy($op, $type, $array = NULL) { * $forum). * - preprocess functions: A list of functions used to preprocess this data. * Ordinarily this won't be used; it's automatically filled in. By default, - * for a module this will be filled in as template_preprocess_HOOK. For - * a theme this will be filled in as phptemplate_preprocess and + * for a module this will be filled in as template_preprocess_HOOK. For a + * theme this will be filled in as phptemplate_preprocess and * phptemplate_preprocess_HOOK as well as themename_preprocess and * themename_preprocess_HOOK. * - override preprocess functions: Set to TRUE when a theme does NOT want the - * standard preprocess functions to run. This can be used to give a theme - * FULL control over how variables are set. For example, if a theme wants - * total control over how certain variables in the page.tpl.php are set, - * this can be set to true. Please keep in mind that when this is used - * by a theme, that theme becomes responsible for making sure necessary - * variables are set. - * - type: (automatically derived) Where the theme hook is defined: - * 'module', 'theme_engine', or 'theme'. + * standard preprocess functions to run. This can be used to give a theme FULL + * control over how variables are set. For example, if a theme wants total + * control over how certain variables in the page.tpl.php are set, this can be + * set to true. Please keep in mind that when this is use by a theme, that + * theme becomes responsible for making sure necessary variables are set. + * - type: (automatically derived) Where the theme hook is defined: 'module', + * 'theme_engine', or 'theme'. * - theme path: (automatically derived) The directory path of the theme or * module, so that it doesn't need to be looked up. * - theme paths: (automatically derived) An array of template suggestions where @@ -2119,14 +2116,16 @@ function hook_taxonomy($op, $type, $array = NULL) { * What 'type' is being processed. This is primarily useful so that themes * tell if they are the actual theme being called or a parent theme. * May be one of: - * - module: A module is being checked for theme implementations. - * - base_theme_engine: A theme engine is being checked for a theme which is a parent of the actual theme being used. - * - theme_engine: A theme engine is being checked for the actual theme being used. - * - base_theme: A base theme is being checked for theme implementations. - * - theme: The actual theme in use is being checked. + * - module: A module is being checked for theme implementations. + * - base_theme_engine: A theme engine is being checked for a theme which is a + * parent of the actual theme being used. + * - theme_engine: A theme engine is being checked for the actual theme being + * used. + * - base_theme: A base theme is being checked for theme implementations. + * - theme: The actual theme in use is being checked. * @param $theme - * The actual name of theme that is being being checked (mostly only useful for - * theme engine). + * The actual name of theme that is being being checked (mostly only useful + * for theme engine). * @param $path * The directory path of the theme or module, so that it doesn't need to be * looked up.