Controllers

Last updated Dec 7th, 2019 | 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

$306 per month—let's make that $500!

Learn more

The Discuss Controllers offer customisation through themes and the theme manifest.php files. This documentation is not yet finished (there's a lot of ground to cover, so to say, and your help is greatly appreciated if you can help out.

Please note that this document deals with web controllers, not mgr controllers powering the back-end component of Discuss.

The Controllers in Discuss¶

Please don't forget to read past this list to see common options and placeholders in the controller templates.

Options¶

Controller Options need to go into the theme's manifest file. If you don't know what that mean, please head over to the Getting Started document!

Controller Template¶

The Controller template is basically the content field of a controller. This contains all the neccessary markup and placeholders for the specific controller to be, like, useful to the visitor. The controller template is wrapped by either the pages/wrapper.tpl or pages/print-wrapper.tpl template.

On the subpages of this document all the different controllers are documented. These contain placeholders specific to that controller. On top of that, some placeholders are available in most (if not all) controllers, and are discussed in this section of this page.

Placeholder	Description
actionbuttons	Buttons generated from the chunks/disactionbutton.chunk.tpl chunk, wrapped in the chunks/disactionbuttons.chunk.tpl chunk. Actions are controller specific and can include login, logout, reply, subscribe, etc. All action buttons are assigned a class of dis-action-action_name where action_name is the name of the action; this can be used to style specific buttons differently.
discuss.user.*	Call uncached. If logged in, the discuss.user.field_name placeholder will contain information about the currently logged in user. Available fields:
	- id
	- username
	- fullname
	- name_first
	- name_last
	- email
	- posts
	- posts_formatted
	- avatar_url
	- isModerator (1 or 0)
	- ... and much more TBA
discuss_version	The current version of Discuss installed.
discuss.pagetitle	Call uncached. Contains the title of the current controller.