$page->renderField() method

Render given $fieldName using site/templates/fields/ markup file

Shorter aliases of this method include:

  • $page->render('fieldName', $file);
  • $page->render->fieldName;
  • $page->_fieldName_;

This method expects that there is a file in /site/templates/fields/ to render the field with:

  • /site/templates/fields/fieldName.php
  • /site/templates/fields/fieldName.templateName.php
  • /site/templates/fields/fieldName/$file.php (using $file argument)
  • /site/templates/fields/$file.php (using $file argument)
  • /site/templates/fields/$file/fieldName.php (using $file argument, must have trailing slash)
  • /site/templates/fields/$file.fieldName.php (using $file argument, must have trailing period)

Note that the examples above showing $file require that the $file argument is specified.

Example

// Render output for the 'images' field (assumes you have implemented an output file)
echo $page->renderField('images');

Usage

// basic usage
$mixed = $page->renderField(string $fieldName);

// usage with all arguments
$mixed = $page->renderField(string $fieldName, string $file = '', $value = null);

Arguments

NameType(s)Description
fieldNamestring

May be any custom field name or native page property.

file (optional)string

Optionally specify file (in site/templates/fields/) to render with (may omit .php extension).

value (optional)mixed, null

Optionally specify value to render, otherwise it will be pulled from this $page.

Return value

mixed string

Returns the rendered value of the field


Hooking $page->renderField(…)

You can add your own hook events that are executed either before or after the $page->renderField(…) method is executed. Examples of both are included below. A good place for hook code such as this is in your /site/ready.php file.

Hooking before

The 'before' hooks are called immediately before each $page->renderField(…) method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.

$this->addHookBefore('Page::renderField', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $page = $event->object;

  // Get values of arguments sent to hook (and optionally modify them)
  $fieldName = $event->arguments(0);
  $file = $event->arguments(1);
  $value = $event->arguments(2);

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $fieldName);
  $event->arguments(1, $file);
  $event->arguments(2, $value);
});

Hooking after

The 'after' hooks are called immediately after each $page->renderField(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('Page::renderField', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $page = $event->object;

  // An 'after' hook can retrieve and/or modify the return value
  $return = $event->return;

  // Get values of arguments sent to hook (if needed)
  $fieldName = $event->arguments(0);
  $file = $event->arguments(1);
  $value = $event->arguments(2);

  /* Your code here, perhaps modifying the return value */

  // Populate back return value, if you have modified it
  $event->return = $return;
});

See Also


$page methods and properties

API reference based on ProcessWire core version 3.0.137

Twitter updates

  • We added WebP image support this year and many have been adopting it in existing projects. We look at a process used for migrating existing websites to WebP images— from preliminary considerations to implementation & testing, w/lots of tips & tricks too: More
    16 August 2019
  • Core version 3.0.137 on the dev branch adds the ability to hook multiple methods at once, in a single call. This post details how it works and provides a useful example of how you might put it to use in your development environment— More
    2 August 2019
  • ProcessWire 3.0.136 updates our CKEditor version and adds a new backtrace() method to the core Debug class— More
    26 July 2019

Latest news

  • ProcessWire Weekly #275
    In the 275th issue of ProcessWire Weekly we're going to walk you through the new features included in ProcessWire 3.0.138, cover some WebP related stuff, and highlight recent forum posts and online resources. Read on!
    Weekly.pw / 17 August 2019
  • WebP images on an existing site
    In this post we’ll look at a process used for migrating an existing website to use WebP images. We’ll cover everything from preliminary considerations to implementation and testing, with lots of tips and tricks along the way.
    Blog / 16 August 2019
  • Subscribe to weekly ProcessWire news

“ProcessWire is like a breath of fresh air. So powerful yet simple to build with and customise, and web editors love it too.” —Margaret Chatwin, Web developer