[TYPO3-project-4-3] Special Configuration for CEs

[Steffen Ritter]

I would prefer such a solution.
When answering you first time I thought about "Template" System.
Introducing a new TS Objekt and a new "branch" in TS this could look like

template {
	10 = TSTEMPLATE (or whatever)
	10 {
		allowPIDs=all
		allowPIDS.recursevely=1
		allowCType=textpix,plugin
		allowCType.plugins=news, commerce, whatever

		renderObjekt = Wrappings of commenting system
		additionalTS = plugin.tt_news >
	}

	20 = TSTEMPLATE
	... and so on
}

In backend wie would have an selector box which shows TS-Templates which 
can be applied (according to PIDS and Ctypes) to this C-Element.

Steffen Kamper schrieb:
> Susanne Moog schrieb:
>> Hello,
>>
>> Daniel Pšötzinger wrote:
>>> Ok for plugins thats an idea: But I would prefer to have this defined 
>>> by the plugin itself (e.g. the plugin can have a field called 
>>> override Typoscript - and it can manage merging the array itself - it 
>>> can even be a idea for extbase and the configuration object)
>>
>> I like the thought of that feature generally and not only for plugins 
>> because it gives a lot of flexibility but I can also understand your 
>> reasoning here.
>>
>> So I had some stray thought I wanted to share:
>>
>> How about a new condition that checks for content element id? We have 
>> a condition check for pages so why not for content elements? With that 
>> it would be possible to have different configurations for elements on 
>> one page but without the loss of a centralized typoscript structure.
>>
>> What do you think?
>>
>> Regards,
>>
>> Susanne
> 
> btw - there are other possibilities also possible:
> 
> define "template scripts" in template that are accessible with a select 
> in CE
> 
> template.news_displaysetting1 {
>     label = Enable special display
>     ts {
>         plugin.tt_news.displayList.option23 = 1
>         }
> }
> 
> take this as a brainstorming variant.
> 
> vg Steffen