Fieldtype::upgrade() method

Called when module version changes

Usage

$fieldtype->upgrade($fromVersion, $toVersion);

Arguments

NameType(s)Description
fromVersion
toVersion

Exceptions

Method can throw exceptions on error:

  • WireException - if upgrade fails


Hooking Fieldtype::upgrade(…)

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

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

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

  /* Your code here, perhaps modifying arguments */

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

Hooking after

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

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

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

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

Fieldtype methods and properties

API reference based on ProcessWire core version 3.0.244

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