[TYPO3-dev] idea: new TCA field type MultiField - a stripped down FlexForm

Steffen Kamper info at sk-typo3.de
Fri Jan 2 15:35:28 CET 2009


Hi Masi,

good that you bring that up.
I think flexforms gives all what you need therefor.

What is missing is a way in TS to address that fields correctly. i 
discussed a lot with Niels this issue, as this is a normal usecase in 
TV, where all fields are in flexforms.

It would be nice to use the XPath in TS to address like
10 = TEXT
10.field = container/el/field

even sections would be accessible with this syntax.

Having some lib giving XML <=> TS functionality would give you a way 
even building flexforms in TS.

This might not cover your idea complete but would lead into this direction.

vg Steffen


Martin Kutschker schrieb:
> Hi!
> 
> FlexForms are great because they are extremely flexible. Unfortunately
> the have therefore some disadvantages when it comes to simpler use cases.
> 
> What I normally want is to habe some fields that don't need to be DB
> selectable stuffed into one DB field (eg plugin configuration). What I
> would want is a to have these fields configurable via page TS and
> accessable via TS in the FE.
> 
> Problems:
> 
> * sections
> * built-in localization that is incompatible to standard-localization
> * default values
> * tying of UI (tabs/sheets) to structure
> 
> Solution:
> 
> A simpler approach that uses only standard TCA configuration options.
> The field definition could be either in XML (FlexForms like) or in PHP
> (standard TCA definition). The data could either be stored in XML or as
> a serialized array. Important is that within a MultiField field names
> are unique: you can shift a field around from sheet to sheet, but it
> will not change its name, so it can always be accessed directly without
> knowing where it is displayed in the UI.
> 
> Masi




More information about the TYPO3-dev mailing list