Skip to main content
FluidTYPO3 home
Documentation
Library
Donate
Search
☾
Templating Manual
Templating Manual
ViewHelper Reference
4.1.1
Use case for custom Flux Controllers
You can opt to use a Flux enabled controller whenever you want your controller to work more closely with your Provider class. Using the controller base gives you automatic access to the Provider and lets the Provider deliver view variables…
4.1.2
Creating custom Flux controllers
A Flux controller is almost exactly identical to a standard ActionController in its most basic form: Once created, the class will automatically be used by Fluid Powered TYPO3's features which render the Content type (in other words…
4.1.3
Differences from standard Controllers
There is not much difference between a standard Extbase plugin "Action Controller" and a Flux enabled controller. The hint lies in the name " enabled" which means a Flux enabled controller is simply an extended controller with a few added…
4.1.4
Controller actions
Your template files inside for example the Content subfolder are according to Extbase conventions connected directly to a Controller's action. In standard Extbase, the Controller action must exist first and will then cause the template file…
