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.236

Latest news

  • ProcessWire Weekly #556
    In the 556th issue of ProcessWire Weekly we're going to share the latest core development news, highlight a new third party module, and more. Read on!
    Weekly.pw / 4 January 2025
  • Custom Fields Module
    This week we look at a new ProFields module named Custom Fields. This module provides a way to rapidly build out ProcessWire fields that contain any number of subfields/properties within them.
    Blog / 30 August 2024
  • 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.