TYPO3 Core

TSConfig per content (tt_content) is needed in addition to the actual Page TSConfig.

Different zones in a single page may contain the same plugin with different customization. In some cases the plugin has great complexity and is not possible to add all the available features to the plugin's flex form.

In this cases the user need to put the extra TS in the page TS config, this is OK for pages with a single instance of the plugin, but under the need of two or more instances the only way to achieve cutomization in each case is to hace TSConfig in a per content basis (adding a TSConfig field to the tt_content table).

Anyway, TSConfig per content seems to be add many possibilities to many extensions.

jp

A real case: You need to add two SINGLE VIEWs of tt_products in a home page, each instance of SINGLE VIEW needs to point a particular product, then you need to define a defaultProductID for each tt_products plugin, per content, not per page. Tt_producs if a very comprenhensive extension and adding every config option to the flexform is not practical, I discussed the situation with Franz Holzinger in the tt_products newsgroup and our conclusion was the need to enhance the template system for this aspects.

(issue imported from #M8332)