ProcessPageEdit::execute() method

Execute the Page Edit process by building the form and checking if it was submitted

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

$string = $processPageEdit->execute();

Return value

string

Exceptions

Method can throw exceptions on error:

  • WireException


Hooking ProcessPageEdit::execute()

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

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

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
});

Hooking after

The 'after' hooks are called immediately after each ProcessPageEdit::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('ProcessPageEdit::execute', 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;

  /* 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.236

Latest news

  • ProcessWire Weekly #541
    In the 541st issue of ProcessWire Weekly we'll share the latest core development news, check out a new module called Search Corrections, and more. Read on!
    Weekly.pw / 21 September 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