ProcessPageEdit::getViewActions() method

Get actions for the "View" dropdown

Usage

// basic usage
$array = $processPageEdit->getViewActions();

// usage with all arguments
$array = $processPageEdit->getViewActions(array $actions = [], bool $configMode = false);

Arguments

NameType(s)Description
actions (optional)array

Actions in case hook wants to populate them

configMode (optional)bool

Specify true if retrieving for configuration purposes rather than runtime purposes.

Return value


Hooking ProcessPageEdit::getViewActions(…)

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

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

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

  /* Your code here, perhaps modifying arguments */

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

Hooking after

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

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

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

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

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