$session->redirect() method

Redirect this session to another URL.

Execution halts within this function after redirect has been issued.

Example

// redirect to homepage
$session->redirect('/'); 

Usage

// basic usage
$session->redirect(string $url);

// usage with all arguments
$session->redirect(string $url, $status = 301);

Arguments

NameType(s)Description
urlstring

URL to redirect to

status (optional)bool, int

One of the following (or omit for 301):

  • true (bool): Permanent redirect (same as 301).
  • false (bool): Temporary redirect (same as 302).
  • 301 (int): Permanent redirect using GET. (3.0.166+)
  • 302 (int): “Found”, Temporary redirect using GET. (3.0.166+)
  • 303 (int): “See other”, Temporary redirect using GET. (3.0.166+)
  • 307 (int): Temporary redirect using current request method such as POST (repeat that request). (3.0.166+)

Hooking $session->redirect(…)

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

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

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

  /* Your code here, perhaps modifying arguments */

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

Hooking after

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

$this->addHookAfter('Session::redirect', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $session = $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)
  $url = $event->arguments(0);
  $status = $event->arguments(1);

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

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

See Also


$session methods and properties

API reference based on ProcessWire core version 3.0.209

Twitter updates

  • ProcessWire 3.0.213 core updates: This week we’ll look at the new WireSitemapXML module, a new WireNumberTools core class, and a new ability for Fieldtype modules to specify useful ready-to-use configurations when creating new fields. More
    24 February 2023
  • ProcessWire 3.0.212 core updates— More
    17 February 2023
  • Adding custom actions to ProcessWire image fields in the admin, part of this week’s dev branch additions: More
    27 January 2023

Latest news

  • ProcessWire Weekly #459
    In the 459th issue of ProcessWire Weekly we're going to check out the latest core updates, introduce a brand-new addition to the ProDevTools family of developer-oriented Pro modules, and more. Read on!
    Weekly.pw / 25 February 2023
  • ProcessWire 3.0.213 core updates
    This week we’ll look at the new WireSitemapXML module, a new WireNumberTools core class, and a new ability for Fieldtype modules to specify useful ready-to-use configurations when creating new fields.
    Blog / 24 February 2023
  • Subscribe to weekly ProcessWire news

“The end client and designer love the ease at which they can update the website. Training beyond how to log in wasn’t even necessary since ProcessWire’s default interface is straightforward.” —Jonathan Lahijani