FieldtypeRepeater::exportValue() method

Export repeater value

If an array is returned, it should only contain: strings, ints, floats or more arrays of those types. This is intended for web service exports.

When applicable, this method should map things like internal IDs to named equivalents (name, path, etc.).

If not overridden, this takes on the same behavior as Fieldtype::sleepValue(). However, if overridden, it is intended to be more verbose than wakeupValue, where applicable.

Usage

// basic usage
$array = $fieldtypeRepeater->exportValue(Page $page, Field $field, RepeaterPageArray $value);

// usage with all arguments
$array = $fieldtypeRepeater->exportValue(Page $page, Field $field, RepeaterPageArray $value, array $options = []);

Arguments

NameType(s)Description
pagePage
fieldField
valueRepeaterPageArray
options (optional)array
  • minimal (bool): Export a minimal array of just fields and values indexed by repeater page name (default=false)

Return value

array


Hooking FieldtypeRepeater::exportValue(…)

You can add your own hook events that are executed either before or after the FieldtypeRepeater::exportValue(…) 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 FieldtypeRepeater::exportValue(…) method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.

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

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

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $page);
  $event->arguments(1, $field);
  $event->arguments(2, $value);
  $event->arguments(3, $options);
});

Hooking after

The 'after' hooks are called immediately after each FieldtypeRepeater::exportValue(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('FieldtypeRepeater::exportValue', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $FieldtypeRepeater = $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)
  $page = $event->arguments(0);
  $field = $event->arguments(1);
  $value = $event->arguments(2);
  $options = $event->arguments(3);

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

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

FieldtypeRepeater methods and properties

API reference based on ProcessWire core version 3.0.244

Latest news

  • ProcessWire Weekly #562
    In the 562nd issue of ProcessWire Weekly we're going to cover the latest core updates, introduce a very interesting triplet of newly released third party modules by Bernhard Baumrock, and more. Read on!
    Weekly.pw / 15 February 2025
  • ProcessWire 3.0.244 new main/master version
    ProcessWire 3.0.244 is our newest main/master/stable version. It's been more than a year in the making and is packed with tons of new features, issue fixes, optimizations and more. This post covers all the details.
    Blog / 18 January 2025
  • Subscribe to weekly ProcessWire news

“Indeed, if ProcessWire can be considered as a CMS in its own right, it also offers all the advantages of a CMF (Content Management Framework). Unlike other solutions, the programmer is not forced to follow the proposed model and can integrate his/her ways of doing things.” —Guy Verville, Spiria Digital Inc.