Controllers deal with objects. They don't define such objects, but provide interfaces to list or edit them, or to get them into action. Outside of thirty bees core, they come as part of modules.

On how to get controllers into modules, see Writing Modules. Following chapters will not the few distinctions between controllers in core and controllers coming with modules. Usually that's the location of files.

These pages were written with the documentation concept of Firefox Add-Ons in mind.

• What are controllers? - Where do they live, what can they do?
• My first controller - A trivial module with a configuration page.
• My second controller - A more advanced module with back office menu entry.
• Anatomy of a controller
• Example controllers

• Back Office Display Engine
• Configuration database table
• File based settings storage
• Database storage
• Internationalization
• Security best practices
• User experience best practices

Note: these display methods aren't exclusive to each other. For example, many controllers provide a list of objects (Products, Categories, Customers, Orders, …) for selection as well as an interface to edit one of them, both with the same controller class. The following methods can get combined.

• Back Office Display Decoration (title, toolbar, etc.)
• Back Office Display Using Templates
• Using Helper for ObjectModel lists
• Using Helper for ObjectModel editing interfaces
• Using Helper For Options (and not database related stuff)

• Do Web Requests With Guzzle (Guzzle is the preferred tool for such requests)

• Helper Fields