About the data structure¶
Basically, the configuration for a FlexForm field is all about pointing to the data structure which contains form rendering information.
For general information about the backbone of a Data Structure, please refer to the “<T3DataStructure>” chapter in the Core API manual.
The mixture of the different “ds” properties can be puzzling at first, but they allow powerful combinations to specify which data structure should be used in different scenarios.
One data structure only¶
'config' => [ 'type' => 'flex', 'ds' => [ 'default' => 'FILE:EXT:myextension/Configuration/FlexForms/Main.xml', ], ],
Straight and simple: Whenever a record is handled that has a column field
definition with this TCA, the data structure defined in
is parsed and the flex form defined in there is displayed.
Data structure selection depends on a field value¶
'config' => [ 'type' => 'flex', 'ds_pointerField' => 'selector' 'ds' => [ 'default' => 'FILE:EXT:myextension/Configuration/FlexForms/Default.xml', 'foo' => 'FILE:EXT:myextension/Configuration/FlexForms/Foo.xml', 'bar' => 'FILE:EXT:myextension/Configuration/FlexForms/Bar.xml', ], ],
There are now multiple data structures registered for this “flex” field. It depends on the value of the field “selector” which one is chosen: If “selector” value is “foo”, “Foo.xml” is parsed and displayed, “Bar.xml” is chosen for the value “bar”, and if none of the two matches, it falls back to “Default.xml”.
Data structure selection depends on a combination of two field values¶
'config' => [ 'type' => 'flex', 'ds_pointerField' => 'list_type,CType', 'ds' => [ 'default' => 'FILE:...', 'tt_address_pi1,list' => 'FILE:EXT:tt_address/pi1/flexform.xml', '*,table' => 'FILE:EXT:css_styled_content/flexform_ds.xml', 'tx_myext_pi1' => 'FILE:EXT:myext/flexform.xml', ], ],
The data structure selection now depends on the values of two different fields. First, there is a general “default” fallback if nothing else matches. Next, if field “list_type” has the value “tt_address_pi1” and “CType” has the value “list”, then the data structure defined in sub array “tt_address_pi1,list” is chosen. If “list_type” is anything, but “CType” is “table”, then the data structure defined in “*,table” is selected. And last, if “list_type” is “tx_myext_pi1” and “CType” is whatever else, then data structure “tx_myext_pi1” is used.
This lookup mechanism is pretty powerful and used for instance in core for data structure selection depending on a selected “tt_content” element plugin.
Data structure lookup with tree traversal¶
'config' => [ 'ds_pointerField' => 'my_ds', 'ds_pointerField_searchParent' => 'pid', ]
The data structure is stored in database field “my_ds” directly. This could be an “type=input” field containing a “FILE:EXT:…” reference, or a “type=text” field with the full data structure. Note that “ds” is not set at all! The trick is that if field “my_ds” of given record is empty, the parent record will be fetched to see if that row contains a value in “my_ds”. The parent record is determined by using the value of field “pid”. This obviously only makes sense for “tree-like” tables like pages. The parent lookup will continue until a value is found, or if the tree root is reached. This lookup allows inheritance of data structure definition to sub pages and sub trees.
Data structure lookup with tree traversal and pointing to a row in a foreign table¶
'config' => [ 'ds_pointerField' => 'my_ds', 'ds_pointerField_searchParent' => 'pid', 'ds_pointerField_searchParent_subField' => 'my_next_ds', 'ds_tableField' => 'foreignTableName:foreignTableField', ]
This is a more complex example to the above one. First note, there is again no “ds” definition. Instead, the code will again traverse a tree up to the root, until a value in “my_next_ds” or “my_ds” is found. The second field “my_next_ds” is preferred if it contains a value over “my_ds” field, if at least one level up was searched. This is also known as the “Template on next level” feature from TemplaVoila.
Additionally, the value within “my_ds” and “my_next_ds” is not treated as the final data structure, but it is the uid of a record in a foreign table. The fields “my_ds” and “my_next_ds” are therefor probably configured as “type=select” fields with a relation to that table. If that row of table “foreignTableName” is found, the content of the field “foreignTableField” is chosen as the final data structure.
The configuration above thus basically says: “Fetch rows up in rootline until you find a value in “ds_pointerField” or “ds_pointerField_searchParent_subField”, treat the content as uid, fetch that record from the foreign table, and use the content of a specific field in there as my data structure”.