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

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

Arguments

NameType(s)Description
pagePage
fieldField
valuearray, int, 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


Hooking FieldtypeComments::exportValue(…)

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

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

FieldtypeComments methods and properties

API reference based on ProcessWire core version 3.0.236

Latest news

  • ProcessWire Weekly #550
    In the 550th issue of ProcessWire Weekly we're going to check out the latest core updates, introduce a new third party module called PagefileMetadata, and more. Read on!
    Weekly.pw / 23 November 2024
  • 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

“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