Form Templating

TYPO3

Description

EXT:form uses Fluid for all frontend output - both for rendering form elements in the browser and for generating email content via the EmailFinisher. Integrators can replace the default Bootstrap-based templates by registering custom paths via YAML. The EmailFinisher requires separate HTML and plaintext templates and includes form values and custom variables inside those templates.

Goals

• I know that EXT:form frontend templates are Bootstrap-based by default and can be replaced by registering custom via YAML
• I know that Form.html is resolved from templateRootPaths and all other form elements as partials from partialRootPaths, named after their formElementTypeIdentifier (e.g. Text.html for a Text element).
• I know that the EmailFinisher always uses FluidEmail and that both an .html and a .txt template file must exist at the configured path.
• I know how to make additional variables available in FluidEmail templates via the variables option in the finisher configuration.
• I know that I need to customize form extension templates in my own site package to prevent changes when updating TYPO3.

Maintainer

Oliver Thiele Web Development Oliver Thiele