Stop execution with a 404 unless redirect URL available (for front-end use)

This is an alternative to using a manual throw new Wire404Exception() and is recognized by PW as a front-end 404 where PagePathHistory (or potentially other modules) are still allowed to change the behavior of the request from a 404 to something else (like a 301 redirect).

Available since version 3.0.146.

Usage

// basic usage
wire404();

// usage with all arguments
wire404(string $message = '');

Arguments

NameType(s)Description
message (optional)string

Optional message to send to Exception message argument (not used in output by default)

Exceptions

Method can throw exceptions on error:

  • Wire404Exception


Functions methods and properties

API reference based on ProcessWire core version 3.0.200

Twitter updates

  • New blog: Debugging tools built-in to ProcessWire. ProcessWire's core comes with a lot of helpful debugging tools and capabilities built-in. In this post we'll cover some of these useful tools and how to use them… More
    1 July 2022
  • A review of weekly core updates, plus a simple recipe for a very effective listing cache—More
    24 June 2022
  • Weekly update: Making ProcessWire render pages at old WordPress URLs (or building a simple/custom URL router in PW): More
    17 June 2022

Latest news

  • ProcessWire Weekly #424
    In the 424th issue of ProcessWire Weekly we'll check out the latest weekly update from Ryan, introduce a new third party module, and more. Read on!
    Weekly.pw / 25 June 2022
  • Debugging tools built into ProcessWire
    ProcessWire's core comes with a lot of helpful debugging tools and capabilities built-in. In this post we'll cover some of these useful tools and how to use them.
    Blog / 1 July 2022
  • 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