Reserved Parameters
Last updated Oct 11th, 2026 | Page history | Improve this page | Report an issue
Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
Backers
Budget
$194 per month—let's make that $500!
Learn moreParameters of custom manager pages and other integrations are free, with a few exceptions.
Reserved parameters in the manager¶
The manager uses these parameters:
a- the action or controllernamespace- the namespace the action belongs to; defaults tocorewhen omittedcontext_key- one of your contexts (e.g. “web” or “mgr”)wctx- the “working context”: the context the current item belongs to, rather than “mgr”class_key- a class name, e.g. when creating a Weblink or static resourceid- the ID a certain action or controller defaults to
action is not a manager parameter — the manager only reads a. Connectors use action to select a processor.
System settings that affect manager routing and assets: manager_theme (picks the theme whose controllers/ and templates/ directories are searched first), welcome_action (the action of the manager’s Welcome page), and manager_path / manager_url (the physical and URL locations of the manager).
Reserved parameters in the front-end¶
q- with friendly URLs enabled, routes a request to the right resource. Changeable via therequest_param_aliassystem setting, but leave it unchanged.id- with friendly URLs disabled, fetches the current resource. Changeable via therequest_param_idsystem setting, but leave it unchanged.
Reserved $_SESSION variables¶
cultureKey- all parameters prefixed with
modx.
Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
Backers
Budget
$194 per month—let's make that $500!
Learn more










