Process modules are self contained applications that run in the ProcessWire admin.

Please be sure to see the Module interface for full details on methods you can specify in a Process module.


Click any linked item for full usage details and examples. Hookable methods are indicated with the icon. In addition to those shown below, the Process class also inherits all the methods and properties of: WireData and Wire.

Show class?             Show args?        

Common

NameReturnSummary 
Process::breadcrumb(string $href, string $label)
$thisAdd a breadcrumb
Process::browserTitle(string $title)
$thisSet the current browser title tag
Process::execute()
string arrayExecute this Process and return the output. You may have any number of execute[name] methods, triggered by URL segments.
Process::getProcessPage()
Page NullPageReturn the Page that this process lives on 
Process::headline(string $headline)
$thisSet the current primary headline to appear in the admin interface
Process::ready()
(nothing)
Process::setConfigData(array $data)
(nothing)

Views

Applicable only to Process modules that are using external output/view files.

NameReturnSummary 
Process::getViewFile()
stringIf a view file has been set, this returns the full path to it. 
Process::getViewVars()
arrayGet all variables set for the output view 
Process::setViewFile(string $file)
$thisSet the file to use for the output view, if different from default. 
Process::setViewVars($key)
$thisSet a variable that will be passed to the output view. 

Module interface

See the Module interface for full details on these methods.

NameReturnSummary 
Process::install()
(nothing)Per the Module interface, Install the module
Process::uninstall()
(nothing)Uninstall this Process
Process::upgrade($fromVersion, $toVersion)
(nothing)Called when module version changes

For hooks

These methods are only useful for hooking and should not be called directly.

NameReturnSummary 
Process::executed(string $method)
(nothing)Hookable method automatically called after execute() method has finished.
Process::installPage()
PageInstall a dedicated page for this Process module and assign it this Process
Process::uninstallPage()
intUninstall (trash) dedicated pages for this Process module

Additional methods and properties

In addition to the methods and properties above, Process also inherits the methods and properties of these classes:

API reference based on ProcessWire core version 3.0.148

Twitter updates

  • ProcessWire 3.0.153 (dev) focuses on comments field updates, significant refactoring/improvements to ProcessWire’s core Template class and PagesLoader class (which is used by the pages API variable), and we introduce a useful new pages API method— More
    20 March 2020
  • ProcessWire 3.0.152 core updates— This week we have some major improvements to our core date/time Inputfield, as well as a new ability to specify your own custom classes for Page objects— More
    6 March 2020
  • This week we’ve got a couple of really useful API-side improvements to the core in 3.0.151, including predefined image settings and static language translation improvements— More
    21 February 2020

Latest news

  • ProcessWire Weekly #307
    In the 307th issue of ProcessWire Weekly we're going to check out the latest dev branch updates, introduce some new third party modules, and more. Read on!
    Weekly.pw / 28 March 2020
  • ProcessWire 3.0.153 core updates
    This latest version of the core on the dev branch focuses on comments field updates, significant refactoring/improvements to ProcessWire’s core Template class and PagesLoader class (which is used by the $pages API variable), and we introduce a useful new $pages API method.
    Blog / 20 March 2020
  • Subscribe to weekly ProcessWire news

I just love the easy and intuitive ProcessWire API. ProcessWire rocks!” —Jens Martsch, Web developer