FlexForms

FlexForms can be used to store data within an XML structure inside a single DB column.

FlexForms can be used to configure content elements (CE) or plugins, but they are optional so you can create plugins or content elements without using FlexForms.

Most of the configuration below is the same, whether you are adding configuration for a plugin or content element. The main difference is how addPiFlexFormValue() is used.

You may want to configure individual plugins or content elements differently, depending on where they are added. The configuration set via the FlexForm mechanism applies to only the content record it has been configured for. The FlexForms configuration for a plugin or CE can be changed by editors in the backend. This gives editors more control over plugin features and what is to be rendered.

Using FlexForms you have all the features of TCA, so it is possible to use input fields, select lists, show options conditionally and more.

Changed in version 12.0: The superfluous array key TCEforms was removed and is not evaluated anymore. Its sole purpose was to wrap real TCA definitions. The TCEforms tags should be removed upon dropping TYPO3 v11 support. In TYPO3 v12 there is an automatic migration that will be removed in a future version.

Example use cases

The bootstrap_package uses FlexForms to configure rendering options, e.g. a transition interval and transition type (slide, fade) for the carousel content element.

../../_images/FlexFormCarousel.png

The carousel content element of EXT:bootstrap_package

Another extensions that utilize FlexForms and can be used as example is:

How it works

  1. In the extension, a configuration schema is defined and attached to one or more content elements or plugins.

  2. When the CE or plugin is added to a page, it can be configured as defined by the configuration schema.

  3. The configuration for this content element is automatically saved to tt_content.pi_flexform.

  4. The extension can read current configuration and act according to the configuration.

Steps to perform (extension developer)

  1. Create configuration schema in T3DataStructure format (XML)

    Example:

    EXT:examples/Configuration/Flexforms/PluginHaikuList.xml
    <T3DataStructure>
        <meta>
            <langDisable>1</langDisable>
        </meta>
        <sheets>
            <sDEF>
                <ROOT>
                    <TCEforms>
                        <sheetTitle>
                            LLL:EXT:examples/Resources/Private/Language/locallang_db.xlf:examples.pi_flexform.sheetGeneral
                        </sheetTitle>
                    </TCEforms>
                    <type>array</type>
                    <el>
                        <settings.singlePid>
                            <TCEforms>
                                <label>
                                    LLL:EXT:examples/Resources/Private/Language/PluginHaiku/locallang_db.xlf:singlePageUid
                                </label>
                                <config>
                                    <type>group</type>
                                    <allowed>pages</allowed>
                                    <maxitems>1</maxitems>
                                    <minitems>0</minitems>
                                    <size>1</size>
                                    <suggestOptions>
                                        <default>
                                            <additionalSearchFields>nav_title, alias, url</additionalSearchFields>
                                            <addWhere>AND pages.doktype = 1</addWhere>
                                        </default>
                                    </suggestOptions>
                                </config>
                            </TCEforms>
                        </settings.singlePid>
                    </el>
                </ROOT>
            </sDEF>
        </sheets>
    </T3DataStructure>
    
  2. The configuration schema is attached to one or more plugins in the folder Configuration/TCA/Overrides of an extension.

    Example for the FlexForm registration of a basic plugin:

    EXT:examples/Configuration/TCA/Overrides/tt_content_plugin_haiku_list.php
    <?php
    
    defined('TYPO3') or die();
    
    \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPlugin(
        [
            'LLL:EXT:examples/Resources/Private/Language/PluginHaiku/locallang_db.xlf:list.title',
            'examples_haiku_list',
            'tx_examples-haiku',
        ],
        'list_type',
        'examples'
    );
    
    $GLOBALS['TCA']['tt_content']['types']['list']['subtypes_excludelist']['examples_haiku_list']='pages,layout,select_key,recursive';
    
    $GLOBALS['TCA']['tt_content']['types']['list']['subtypes_addlist']['examples_haiku_list']='pi_flexform';
    
    \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPiFlexFormValue(
        'examples_haiku_list',
        'FILE:EXT:examples/Configuration/Flexforms/PluginHaikuList.xml'
    );
    

    New in version 12.0: The method ExtensionUtility::registerPlugin() returns the plugin signature.

    When registering Extbase plugins you can use the return value of ExtensionUtility::registerPlugin() to figure out the plugin signature to use:

    EXT:blog_example/Configuration/TCA/Overrides/tt_content.php (Excerpt)
    $pluginSignature = ExtensionUtility::registerPlugin(
        'blog_example',
        'Pi1',
        'A Blog Example',
    );
    $GLOBALS['TCA']['tt_content']['types']['list']['subtypes_addlist'][$pluginSignature]
        = 'pi_flexform';
    ExtensionManagementUtility::addPiFlexFormValue(
        $pluginSignature,
        'FILE:EXT:blog_example/Configuration/FlexForms/PluginSettings.xml'
    );
    

    If you are using a content element instead of a plugin, the example looks like this:

    EXT:my_extension/Configuration/TCA/Overrides/tt_content.php
    \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPiFlexFormValue(
        // 'list_type' does not apply here
        '*',
        // FlexForm configuration schema file
        'FILE:EXT:example/Configuration/FlexForms/Registration.xml',
        // ctype
        'accordion'
    );
    

    Finally, according to "Configuration of the displayed order of fields in FormEngine and their tab alignment." the field containing the FlexForm still needs to be added to the showitem directive. The following example shows line from the accordion element of the Bootstrap Package.

    EXT:your_extension/Configuration/TCA/Overrides/tt_content.php
    // Configure element type
    $GLOBALS['TCA']['tt_content']['types']['accordion'] = array_replace_recursive(
        $GLOBALS['TCA']['tt_content']['types']['accordion'],
        [
            'showitem' => '
                --div--;General,
                --palette--;General;general,
                --palette--;Headers;headers,
                tx_bootstrappackage_accordion_item,
                --div--;Options,
                pi_flexform'
        ]
    );
    
  3. Access the settings in your extension:

    The settings can be read using one of the methods described below, e.g. from an Extbase controller action, from a PHP function (without using the Extbase framework), from TypoScript or from within a Fluid template.

More examples

The definition of the data types and parameters used complies to the column types defined by TCA.

The settings must be added within the <el> element in the FlexForm configuration schema file.

Select field

<settings.orderBy>
    <label>
        LLL:EXT:example/Resources/Private/Language/Backend.xlf:settings.registration.orderBy
    </label>
    <config>
        <type>select</type>
        <renderType>selectSingle</renderType>
        <items>
            <numIndex index="0">
                <numIndex index="0">
                    LLL:EXT:example/Resources/Private/Language/Backend.xlf:settings.registration.orderBy.crdate
                </numIndex>
                <numIndex index="1">crdate</numIndex>
            </numIndex>
            <numIndex index="1">
                <numIndex index="0">
                    LLL:EXT:example/Resources/Private/Language/Backend.xlf:settings.registration.orderBy.title
                </numIndex>
                <numIndex index="1">title</numIndex>
            </numIndex>
        </items>
    </config>
</settings.orderBy>

See also

Populate a select field with a PHP Function (itemsProcFunc)

<settings.orderBy>
    <label>
        LLL:EXT:example/Resources/Private/Language/Backend.xlf:settings.registration.orderBy
    </label>
    <config>
        <type>select</type>
        <itemsProcFunc>Myvendor\Example\Backend\ItemsProcFunc->user_orderBy
        </itemsProcFunc>
        <renderType>selectSingle</renderType>
        <items>
            <!-- empty by default -->
        </items>
    </config>
</settings.orderBy>

The function user_orderBy populates the select field in BackendItemsProcFunc.php:

class ItemsProcFunc
{
     /**
     * Modifies the select box of orderBy-options.
     *
     * @param array &$config configuration array
     */
    public function user_orderBy(array &$config)
    {
        // simple and stupid example
        // change this to dynamically populate the list!
        $config['items'] = [
            // label, value
            ['Timestamp', 'timestamp'],
            ['Title', 'title']
        ];
    }

    // ...
}

How this looks when configuring the plugin:

../../_images/FlexFormsItemsProcFunc.png

See also

Display fields conditionally (displayCond)

Some settings may only make sense, depending on other settings. For example in one setting you define a sorting order (by date, title etc.) and all sort orders except "title" have additional settings. These should only be visible, if sort order "title" was not selected.

You can define conditions using displayCond. This dynamically defines whether a setting should be displayed when the plugin is configured. The conditions may for example depend on one or more other settings in the FlexForm, on database fields of current record or be defined by a user function.

<config>
    <type>select</type>
</config>
<!-- Hide field if value of neighbour field "settings.orderBy" on same sheet is not "title" -->
<displayCond>FIELD:settings.orderBy:!=:title</displayCond>

Again, the syntax and available fields and comparison operators is documented in the TCA reference:

See also

Reload on change

Especially in combination with conditionally displaying settings with displayCond, you may want to trigger a reloading of the form when specific settings are changed. You can do that with:

<onChange>reload</onChange>
<config>
    <!-- ... -->
</config>

The onChange element is optional and must be placed on the same level as the <config> element.

How to read FlexForms from an Extbase controller action

The settings can be read using $this->settings in an Extbase controller.

$includeCategories = (bool) ($this->settings['includeCategories'] ?? false);

Important

If you wish to access a setting from your controller via $this->settings, the name of the setting must be prefixed with settings., so literally settings directly followed by a dot (.).

Read FlexForms values in PHP

You can use the FlexFormService to read the content of a FlexForm field:

EXT:my_extension/Classes/Controller/NonExtbaseController.php
use TYPO3\CMS\Core\Service\FlexFormService;
use TYPO3\CMS\Core\Utility\GeneralUtility;

final class NonExtbaseController
{

    // Inject FlexFormService
    public function __construct(
        private readonly FlexFormService $flexFormService,
    ) {
    }

    // ...

    private function loadFlexForm($flexFormString): array
    {
        return $this->flexFormService
            ->convertFlexFormContentToArray($flexFormString);
    }
}

Using FlexFormService->convertFlexFormContentToArray the resulting array can be used conveniently in most use cases:

 var_export(
     $this->flexFormService->convertFlexFormContentToArray($flexFormString)
 );

/* Output:
[
    'settings' => [
        'singlePid' => 25,
        'listPid' => 380,
    ],
]
*/

The result of GeneralUtility::xml2array() preserves the internal structure of the XML FlexForm, and is usually used to modify a FlexForm string. See section How to modify FlexForms from PHP for an example.

var_export(GeneralUtility::xml2array($flexFormString)));

/* Output:
[
    'data' =>
        [
            'sDEF' =>
                [
                    'lDEF' =>
                        [
                            'settings.singlePid' =>['vDEF' => '4',],
                            'settings.listPid' =>['vDEF' => '',],
                        ],
                ],
        ],
];
*/

How to modify FlexForms from PHP

Some situation make it necessary to modify FlexForms via PHP.

In order to convert a FlexForm to a PHP array, preserving the structure, the xml2array method in GeneralUtility can be used to read the FlexForm data, then the FlexFormTools can be used to write back the changes.

use \TYPO3\CMS\Core\Utility\GeneralUtility;
use \TYPO3\CMS\Core\Configuration\FlexForm\FlexFormTools;

$flexFormArray = GeneralUtility::xml2array($flexFormString);
$changedFlexFormArray = $this->doSomething($flexFormArray);

$flexFormTools = new FlexFormTools();
$flexFormString = $flexFormTools->flexArray2Xml($changedFlexFormArray, addPrologue: true);

How to access FlexForms From TypoScript

It is possible to read FlexForm properties from TypoScript:

lib.flexformContent = CONTENT
lib.flexformContent {
    table = tt_content
    select {
        pidInList = this
    }

    renderObj = COA
    renderObj {
        10 = TEXT
        10 {
            data = flexform: pi_flexform:settings.categories
        }
    }
}

The key flexform is followed by the field which holds the FlexForm data (pi_flexform) and the name of the property whose content should be retrieved (settings.categories).

How to access FlexForms from Fluid

If you are using an Extbase controller, FlexForm settings can be read from within a Fluid template using {settings}. See the note on naming restrictions in How to Read FlexForms From an Extbase Controller Action.

If you defined your FLUIDTEMPLATE in TypoScript, you can assign single variables like that:

my_content = FLUIDTEMPLATE
my_content {
  variables {
    categories = TEXT
    categories.data = flexform: pi_flexform:categories
  }
}

In order to have all FlexForm fields available, you can use the FlexFormProcessor. See also FlexFormProcessor in the TypoScript Reference. This example would make your FlexForm data available as Fluid variable {flexform}:

my_content = FLUIDTEMPLATE
my_content {
  dataProcessing {
    10 = TYPO3\CMS\Frontend\DataProcessing\FlexFormProcessor
    10.fieldName = my_flexform_field
    10.as = myOutputVariable
  }
}

See also

FlexFormProcessor.

Steps to Perform (Editor)

After inserting a plugin, the editor can configure this plugin by switching to the tab "Plugin" or whatever string you defined to replace this.

../../_images/FlexformBackend.png

Credits

Some of the examples were taken from the extensions EXT:news (by Georg Ringer) and EXT:bootstrap_package (by Benjamin Kott).

Further enhancements by the TYPO3 community are welcome!