FieldtypeOptions::importConfigData() method

Convert an array of exported data to a format that will be understood internally (opposite of exportConfigData)

This is the opposite of the exportConfigData() method. Most modules can use the default implementation provided here.

Usage

$array = $fieldtypeOptions->importConfigData(Field $field, array $data);

Arguments

NameType(s)Description
fieldField
dataarray

Return value

array

Data as given and modified as needed. Also included is $data[errors], an associative array indexed by property name containing errors that occurred during import of config data.


Hooking FieldtypeOptions::importConfigData(…)

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

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

  // Get values of arguments sent to hook (and optionally modify them)
  $field = $event->arguments(0);
  $data = $event->arguments(1);

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $field);
  $event->arguments(1, $data);
});

Hooking after

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

$this->addHookAfter('FieldtypeOptions::importConfigData', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $FieldtypeOptions = $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)
  $field = $event->arguments(0);
  $data = $event->arguments(1);

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

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

FieldtypeOptions 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