Field types (config > type)

The field types get defined in the TCA of a field in ['config']['type']. The field type influences the rendering of the form field in the backend. It also influences the processing of data on saving the values. Those behaviour can be influenced by further properties.

Section ['columns'][*]['config'] (where * stands for a table column) is the main workhorse when it comes to single field configuration. The main property is type, it specifies the DataHandler processing and database value. Additionally, property renderType specifies how a field is rendered. The renderType is sometimes optional. Both properties together specify the set of properties that are valid for one field.

This section of the documentation is first split by type to give an overview of what can be done with a type, then lists all possible renderType's with all possible properties. Since some type's can do useful stuff without a specific renderType too, those properties are listed below renderType "default", which equals to "not set".

An overview of available types:

check

One or multiple check boxes

flex

Form elements stored in an XML structure in one field.

group

Relations to other table rows or files.

imageManipulation

Json array with cut / cropping information. Special field for images in FAL / Resource handling.

inline

Relations to other table rows that can be edited in the same form. Also used for file resources via sys_file_reference table.

input

Single line text input. Used for a various different single line outputs like head lines, links, color pickers.

none

Read only, virtual field. No DataHandler processing.

passthrough

Not displayed, only send as hidden field to DataHandler.

radio

One or multiple radio buttons.

select

Select one or more items from a list.

slug

Define parts of a URL path

text

A multiline text field. Used for RTE display, code editor and some more.

user

Special rendering and evaluation defined by an additional node in the form engine