Email 

Controls the autocomplete attribute of a given email field. If set to true, adds attribute autocomplete="on" to the email input field allowing browser auto filling the field:

'autocomplete' => true,

Configuration of field evaluation.

Some of these evaluation keywords will trigger a JavaScript pre- evaluation in the form. Other evaluations will be performed in the backend. The evaluation functions will be executed in the list-order. Keywords:

unique

Requires the field to be unique for the whole table. Evaluated on the server only.

Note

When selecting on unique-fields, make sure to select using AND pid>=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!

uniqueInPid

Requires the field to be unique for the current PID among other records on the same page. Evaluated on the server only.

For details see fieldInformation.

Possible keywords: useOrOverridePlaceholder

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 .

If set to true, a checkbox will appear, which by default deactivates the field. In the deactivated state the field is saved as NULL in the database. By activating the checkbox it is possible to set a value. If nothing is entered into the field, then an empty string will be saved and not a NULL .

When the eval option is set to unique or uniqueInPid multiple null values are still possible.

The database field must allow the NULL value.

Placeholder, containing a default date.

<?php

use TYPO3\CMS\Core\Utility\ExtensionManagementUtility;

defined('TYPO3') or die();

ExtensionManagementUtility::addTCAcolumns('tx_myextension_conference', [
  'contact_email' => [
    'label' => 'my_extension.db:conference.contact_email',
    'config' => [
      'type' => 'email',
      'placeholder' => 'info@example.org',
      // The addresses of the organizers to choose from
      'valuePicker' => [
        'items' => [
          [
            'label' => 'my_extension.db:conference.contact_email.info',
            'value' => 'info@example.org',
          ],
          [
            'label' => 'my_extension.db:conference.contact_email.program',
            'value' => 'program@example.org',
          ],
          [
            'label' => 'my_extension.db:conference.contact_email.sponsoring',
            'value' => 'sponsoring@example.org',
          ],
        ],
      ],
      'behaviour' => [
        'allowLanguageSynchronization' => true,
      ],
    ],
  ],
]);
ExtensionManagementUtility::addToAllTCAtypes(
  'tx_myextension_conference',
  'contact_email',
  '',
  'before:--div--;core.form.tabs:categories',
);

Renders the field in a way that the user can see the values but cannot edit them. The rendering is as similar as possible to the normal rendering but may differ in layout and size.

If set to true a non-empty value is required in the field. Otherwise the form cannot be saved.

By default, all fields of type email are considered searchable. To exclude a field from being searchable, set the following in the field's TCA configuration:

'searchable' => false,

Abstract value for the width of the <input> field. To set the email field to the full width of the form area, use the value 50. Minimum is 10. Default is 30.

Renders a list of email addresses to choose from below the field. The editor can still type another address. When the editor selects an item, its value replaces the current value of the field.

items (array)

A list of selectable items. Each item is an associative array: ['label' => 'Shown label', 'value' => 'info@example.org'] . The label can be plain text or a label reference.