How to print a field in node.tpl.php without labels or markup?

Question

In Drupal 7, you can render a field in a tpl.php file like this:

But that prints it out with it's label and HTML. Is there a way to get just the raw value of the field.

I know you can do the following:

• Override the field markup in the field.tpl.php file (or field--FIELDNAME.tpl.php)
• Turn off labels in the admin interface
• Use a module like Fences to control mark up in the admin interface.

However, all of those involve extra steps. I was wondering if there is a way to do it directly in the node.tpl.php file. That way, all the changes are contained in a single place. (Plus if you change themes to one that requires the labels, you have to go back in the admin interface and turn them back on).

Answer 1

If you just want the value of a given field, it will be in the $node object in your node.tpl.php file (or node--type.tpl.php).

Normally it's under something like:

$node->field_name['und'][0]['value']

Answer 2

You're on the right track!

Rather than a node template file though, the individual markup of a field is controlled by its field.tpl.php file. You can control the display of a field in a very granular way by making a custom one - copy your theme's default implementation of it, name the copy field--field-name.tpl.php, and remove all the excess markup.

Answer 3

You might want to try

<?php print render($content['field_your_field']); ?>

in node.tpl.php combined with context and entity view modes modules or simply modify the display settings of the field in the content type configuration

Answer 4

If you are in the node template you can load the field, then get the content from the loaded field. Check out the field_get_items documentation for more info. In short it returns the values you want in the current language.

$field_name = 'your_field_here';
$field= field_get_items('node', $node, $field_name);
print $field[0]['value']

should do it. It will return an element for each item if it is a multi value field. They can be accessed via $field[$key]['value']

Answer 5

wolffer-east's answer satisfies the original question goals of:

• Printing a field
• Doing it in a single file (so everything is in one place).

However, the code is quite complex for a node.tpl.php file which are only supposed to contain simple PHP statements.

So in the end, I reworked it as follows. In my template PHP file, I put the following:

function print_field($field_name) {

if (arg(0) == 'node' && is_numeric(arg(1))) {
  // Get the nid
  $nid = arg(1);

  // Load the node if you need to
  $node = node_load($nid);
}

$field= field_get_items('node', $node, $field_name);
print $field[0]['value'];
} 

This is the same as wolffer-east, except it loads the node.

In my node file, I can then use the following:

<?php print_field('field_body_text') ?>

This renders out the field without any labels and HTML, but still clean.

---

A more advance version is this:

In template.php function print_field($field_name, $format = 'safevalue') {

if (arg(0) == 'node' && is_numeric(arg(1))) {
  // Get the nid
  $nid = arg(1);

  // Load the node if you need to
  $node = node_load($nid);
}

$field= field_get_items('node', $node, $field_name);

if ($format = 'url') {
    print file_create_url($field[0]['uri']);
} else {

print $field[0][$format];
}
}

In node.tpl.php

You can swap 'filename' with any of the following:

• value: Prints field without any extra HTML for paragraphs and line breaks
• safe_value: Prints field HTML for paragraphs and line breaks
• filename: Prints field's filename uri: Prints field's path in public:// format[*]
• url: Prints field's path in traditional URL format[*]
• alt: Prints field's alt value[*]
• title: Prints field's title value[*]
• width: Prints field's width value[*]
• height: Prints field's height value[*]

[*] only applies to fields that have files/images

The only downside is that it displays the following error message:

Notice: Undefined index: safevalue in print_field() (line 16 of template.php)

I am not sure how to fix this error message, but I guess it is a separate question.