FieldtypeFile::exportValue() method

Export 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 = $fieldtypeFile->exportValue(Page $page, Field $field, $value);

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

Arguments

NameType(s)Description
pagePage
fieldField
valuearray, float, int, null, object, string
options (optional)array

Optional settings to shape the exported value, if needed:

  • system (boolean): Indicates value is being used for a system export via $pages->export() call (default=false).
  • human (boolean): When true, Fieldtype may optionally emphasize human readability over importability (default=false).

Return value

array float int string


Hooking FieldtypeFile::exportValue(…)

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

$this->addHookBefore('FieldtypeFile::exportValue', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $FieldtypeFile = $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 FieldtypeFile::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('FieldtypeFile::exportValue', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $FieldtypeFile = $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;
});

FieldtypeFile methods and properties

API reference based on ProcessWire core version 3.0.248

Latest news

  • ProcessWire Weekly #581
    The 581st issue of ProcessWire Weekly brings in all the latest news from the ProcessWire community. Modules, sites, and more. Read on!
    Weekly.pw / 28 June 2025
  • New ProcessWire admin redesign
    When you upgrade to ProcessWire 3.0.248 or newer (currently the dev branch), you’ll immediately notice something new and beautiful…
    Blog / 9 May 2025
  • Subscribe to weekly ProcessWire news

“I am currently managing a ProcessWire site with 2 million+ pages. It’s admirably fast, and much, much faster than any other CMS we tested.” —Nickie, Web developer