/[drupal]/contributions/modules/views/theme/views-view-field.tpl.php
ViewVC logotype

Contents of /contributions/modules/views/theme/views-view-field.tpl.php

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (show annotations) (download) (as text)
Fri May 16 22:22:32 2008 UTC (18 months, 1 week ago) by merlinofchaos
Branch: MAIN
CVS Tags: DRUPAL-6--2-7, DRUPAL-6--2-6, DRUPAL-6--2-5, DRUPAL-6--2-4, DRUPAL-6--2-3, DRUPAL-6--2-2, DRUPAL-6--2-1, DRUPAL-6--2-0, DRUPAL-6--3-0-ALPHA1, DRUPAL-6--2-0-BETA3, DRUPAL-6--2-0-BETA4, DRUPAL-6--2-0-RC5, DRUPAL-6--2-0-RC4, DRUPAL-6--2-0-RC3, DRUPAL-6--2-0-RC1, DRUPAL-6--2-0-RC2, HEAD
Branch point for: DRUPAL-6--2, DRUPAL-6--3, DRUPAL-7--3
File MIME type: text/x-php
Create a default preprocess for the "field" theme and make a real template that just will not get used unless copied into a theme.
1 <?php
2 // $Id$
3 /**
4 * This template is used to print a single field in a view. It is not
5 * actually used in default Views, as this is registered as a theme
6 * function which has better performance. For single overrides, the
7 * template is perfectly okay.
8 *
9 * Variables available:
10 * - $view: The view object
11 * - $field: The field handler object that can process the input
12 * - $row: The raw SQL result that can be used
13 * - $output: The processed output that will normally be used.
14 *
15 * When fetching output from the $row, this construct should be used:
16 * $data = $row->{$field->field_alias}
17 *
18 * The above will guarantee that you'll always get the correct data,
19 * regardless of any changes in the aliasing that might happen if
20 * the view is modified.
21 */
22 ?>
23 <?php print $output; ?>

  ViewVC Help
Powered by ViewVC 1.1.2