The behaviour array contains various sub properties to specify processing options like
localization overlay behaviour and children behaviour for relation types. Available properties
vary by type and renderType combination.
Allows an editor to select in a localized record whether the value is copied
over from default or source language record, or if the field has an own value
in the localization. If set to true and if the table supports localization
and if a localized record is edited, this setting enables FieldWizard
Two or three radio buttons shown below the field input. The state of this is
stored in a json encoded array in the database table called l10n_state.
It tells the DataHandler which fields of the localization records should be kept
in sync if the underlying default or source record changes.
performed in the backend. The evaluation functions will be executed in the list-order. Keywords:
Allows only a-zA-Z characters.
Same as “alpha” but allows also “0-9”
Same as “alphanum” but allows also “_” and “-” chars.
Allows a domain name such as “example.com” and automatically transforms
the value to punicode if needed.
Converts the input to a floating point with 2 decimal positions, using the “.” (period) as the decimal
delimited (accepts also “,” for the same).
This type adds a server-side validation of an email address. If the input does not contain a valid email
address, a flash message warning will be displayed.
Evaluates the input to an integer.
Will filter out any character in the input string which is not found in the string entered in the
Converts the string to lowercase (only A-Z plus a selected set of Western European special chars).
Removes all occurrences of space characters (chr(32))
An empty value (string) will be stored as NULL in the database, requires a proper sql definition.
Allows only 0-9 characters in the field.
Will show “*******” in the field after entering the value and moving to another field. Thus passwords
can be protected from display in the field.
The value is visible while it is being entered!
A non-empty value is required in the field (otherwise the form cannot be saved).
The value will be hashed using the password hash configuration for BE for all tables except fe_user,
where the password hash configuration for FE is used. Note this eval is typically only used core internally
for tables be_users and fe_users on the password field.
The value in the field will have white spaces around it trimmed away.
Requires the field to be unique for the whole table. Evaluated on the server only.
When selecting on unique-fields, make sure to select using ANDpid>=0 since the field can contain
duplicate values in other versions of records (always having PID = -1). This also means that if you are using
versioning on a table where the unique-feature is used you cannot set the field to be truly unique
in the database either!
Requires the field to be unique for the current PID among other records on the same page.
Evaluated on the server only.
Converts to uppercase (only A-Z plus a selected set of Western European special chars).
Evaluates the input to a year between 1970 and 2038. If you need any year, then use “int” evaluation instead.
User defined form evaluations.
Trimming the value for white space before storing in the database:
By this configuration the field will be stripped for any space characters, converted to lowercase, only accepted
if filled in and on the server the value is required to be unique for all records from this table:
You can supply own form evaluations in an extension by creating a class with three functions, one which returns
deevaluateFieldValue() called when opening the record and evaluateFieldValue() called for validation when
saving the record:
// Register the class to be available in 'eval' of TCA$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tce']['formevals']['Vendor\\Extension\\Evaluation\\ExampleEvaluation']='';
Show action buttons next to the element. This is used in various type’s to add
control buttons right next to the main element. They can open popus, switch the entire view
and other things. All must provide a “button” icon to click on, see
FormEngine docs for more details.
See type=group for examples.
The link browser control is typically used with type='input' with renderType='inputLink' adding a button
which opens a popup to select an internal link to a page, an external link or a mail address.
pid of the new record. Can be an hard pid setting, or one of these markers, see
Falls back to “current pid” if not set, forces pid=0 if records of this table are only
allowed on root level.
allowedExtensions (string, list)
Comma separated list of allowed file extensions. By default, all extensions are allowed.
blindLinkFields (string, list)
Comma separated list of link fields that should not be displayed. Possible values are
class, params, target and title. By default, all link fields are displayed.
blindLinkOptions (string, list)
Comma separated list of link options that should not be displayed. Possible values are
file, mail, page, spec, and url. By default, all link options are displayed.
title (string or LLL reference)
Allows to set a different ‘title’ attribute to the popup icon, defaults
Allows to set a different size of the popup, defaults
Show information between an element label and the main element input area. Configuration
works identical to the “fieldWizard” property, no default configuration in the core exists (yet).
In contrast to “fieldWizard”, HTML returned by fieldInformation is limited, see
FormEngine docs for more details.
It is possible to add own wizards by adding them to the TCA of the according field and pointing to a registered
renderType, to resort wizards by overriding the before and after keys, to hand over additional
options in the optional options array to specific wizards, and to disable single wizards using the
disabled key. Developers should have a look at the
FormEngine docs for details.
The following fieldWizards are available for this renderType:
Show a “diff-view” if the content of the default language record has been changed after the
translation overlay has been created. The [‘ctrl’] section property
transOrigDiffSourceField has to be specified
to enable this wizard in a translated record.
This wizard is important for editors who maintain translated records: They can see what has been
changed in their localization parent between the last save operation of the overlay.
A field has been changed in default language record
The localization state selector wizard displays two or three radio buttons in localized records
saying: “This field has an own value distinct from my default language or source record”, “This field
has the same value as the default language record” or “This field has the same value as my source record”.
This wizard is especially useful for the tt_content table. It will only render, if:
The record is a localized record (not default language)
The record is in “translated” (connected), but not in “copy” (free) mode
Show values from the default language record and other localized records if the edited row is a
localized record. Often used in tt_content fields. By default, only the value of the default
language record is shown, values from further translations can be shown by setting the
userTsConfig property additionalPreviewLanguages.
The wizard shows content only for “simple” fields. For instance, it does not work for database relation fields,
and if the field is set to readOnly. Additionally, the table has to be language aware by setting up the
according fields in [‘ctrl’] section.
Header field showing values from two other languages
If the evaluation type “is_in” (see eval) is used for evaluation, then
the characters in the input string should be found in this string as well. This value is also passed
as argument to the evaluation function if a user-defined evaluation function is registered.
The “is_in” value is trimmed during processing, leading and trailing whitespaces are removed. If
whitespaces should be allowed, it should be in between other characters, example ab.
This property is related to the placeholder property. When defined a checkbox will appear above the field. If that
box is checked, the field can be used to enter whatever the user wants as usual. If the box is not checked, the
field becomes read-only and the value saved to the database will be NULL.
What impact this has in the frontend depends on what is done in the code using this field. In the case of
FAL relations, for example, if the “title” field has its box checked, the “title” from the
related metadata will be provided.
This is how the mode checkbox appears in the TYPO3 CMS backend:
Several fields with their placeholder override checkboxes
In order for this property to apply properly, the field must be allowed to use “NULL” as a value,
the “eval” property must list “null” as a possible evaluation.
Placeholder text for the field. This can be a simple string or a reference to a value in the current record
or another one. With a syntax like __row|field the placeholder will take
the value of the given field from the current record.
This can be recursive to follow a longer patch in a table record chain. If the designated field is a relation to
another table (is of type select, group or
inline), the related record will be loaded and the placeholder searched within it.
In the above placeholder syntax, uid_local points to the related “sys_file” record and metadata
points to the “sys_file_metadata” of the related “sys_file” record. From there we take the content
of the title field as placeholder value.
Render a value slider next to the field. Only works for fields evaluated
to integer and float. It is advised to also define a range property,
otherwise the slider will go from 0 to 10000. Note the range can be negative if needed. Available keys:
step (integer / float)
Set the step size the slider will use. For floating point values this can itself be a floating point value.