$process->execute() method

Retrieve a page, check access, and render

When any execute() method returns a string, it us used as the actual output. When the method returns an associative array, it is considered an array of variables to send to the output view layer. Returned array must not be empty, otherwise it cannot be identified as an associative array.

This execute() method is called when no URL segments are present. You may have any number of execute() methods, i.e. executeFoo() would be called for the URL ./foo/ and executeBarBaz() would be called for the URL ./bar-baz/.

Usage

// basic usage
$string = $process->execute();

// usage with all arguments
$string = $process->execute(bool $internal = true);

Arguments

NameType(s)Description
internal (optional)bool

True if request should be internally processed. False if PW is bootstrapped externally.

Return value

string

Output of request


Hooking $process->execute(…)

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

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

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

  /* Your code here, perhaps modifying arguments */

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

Hooking after

The 'after' hooks are called immediately after each $process->execute(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('ProcessPageView::execute', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $process = $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)
  $internal = $event->arguments(0);

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

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

$process methods and properties

API reference based on ProcessWire core version 3.0.236

Latest news

  • ProcessWire Weekly #554
    In the 554th issue of ProcessWire Weekly we'll check out the latest core updates, introduce a couple of new third party modules, and more. Read on!
    Weekly.pw / 21 December 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

“We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like superbude.de. ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH