[TYPO3-core] RFC: Feature #6770: Implement option to use different Flexform Datastructures per type field value

Steffen Kamper steffen at sk-typo3.de
Fri Nov 23 01:20:39 CET 2007


"Ingmar Schlecht" <ingmar at typo3.org> schrieb im Newsbeitrag 
news:mailman.1.1195685420.13243.typo3-team-core at lists.netfielders.de...
> Hi Masi,
>
> Martin Kutschker schrieb:
>> We could use a * or the blank for a catchall
>>
>> But I think we can have this even shorter:
>>
>> 'ds_pointerfield' => 'list_type,CType',
>> 'ds' => array(
>>     'auxdataviewer_pi1' => 'FILE:EXT:auxdataviewer/pi1/flex.xml',
>>      '*,table' => 'FILE:EXT:csc/flex.xml',
>>      'tt_address_pi1,list' => 'FILE:EXT:.../...xml',
>>  ),
>
> Sounds good, attached is a new patch.
>
> The pointer fields are limited to two fields though, implementing it for
> an arbitrary amount of fields would get too complex.
>
> cheers
> Ingmar
>
> -- 
> Ingmar Schlecht
> TYPO3 Association Active Member
>

+1 after testing.

I tested with the felogin extension (CType) and the inclusion mentioned by 
Ingmar:
$TCA['tt_content']['columns']['pi_flexform']['config']['ds']['*,login'] = 
'FILE:EXT:'.$_EXTKEY.'/flexform.xml';

works perfect ;-)

I tried it witt a normal extension added to list, the syntax is slightly 
different as you don't have to use the tx_
so i did with newloginbox and got it with

$TCA['tt_content']['columns']['pi_flexform']['config']['ds']['newloginbox_pi1,list'] 
= 'FILE:EXT:newloginbox/flexform_ds.xml';
or
$TCA['tt_content']['columns']['pi_flexform']['config']['ds']['newloginbox_pi1] 
= 'FILE:EXT:newloginbox/flexform_ds.xml';

works perfect.
But why should i use list as second parameter is optional, is there any 
other possibility?

I don't think that more than 2 parameters needed.

vg   Steffen 




More information about the TYPO3-team-core mailing list