You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the feature request "Add custom TypoScript to Content Block," which I find very valuable (especially regarding Data Processors), I would like to propose considering TSconfig at the same time.
I encountered a similar issue with the following requirement:
I am using …
basics:
- TYPO3/Appearance
… in the config.yaml file and need to adjust the displayed layout options. It would be great if the following configuration could be handled directly within the element's directory:
TCEFORM.tt_content.layout {
# remove layout options 1-3 from all FSC CTypes
removeItems = 1,2,3
types {
my_element {
altLabels {
0 = 3-Columns
1 = 2-Columns
2 = Mixed
}
# change "removeItems" for this CType to re-allow options 1-2
removeItems = 3
}
}
}
I can also imagine additional use cases that go beyond TCEFORM.tt_content (and data processors in the TypoScript case). For example, configuring a linkHandler for the element, which requires both TypoScript and TSconfig.
Therefore, it would likely be beneficial if both aspects—TSconfig and TypoScript—could be fully configurable via page.tsconfig and setup.typoscript files located directly in the element's directory.
The text was updated successfully, but these errors were encountered:
Thanks for the feature request. We are aware of the desire to bundle everything you need including TypoScript and TSConfig into the Content Block. But this needs to go hand in hand with Site Sets, which allow scoping for sites. If we would introduce an own autoload feature for this, it would always be global. Hence, this is probably something for TYPO3 v14, where Content Blocks is an integral part of the Core and works together with Site Sets (Scoped Content Blocks per site).
In addition to the feature request "Add custom TypoScript to Content Block," which I find very valuable (especially regarding Data Processors), I would like to propose considering TSconfig at the same time.
I encountered a similar issue with the following requirement:
I am using …
… in the config.yaml file and need to adjust the displayed layout options. It would be great if the following configuration could be handled directly within the element's directory:
I can also imagine additional use cases that go beyond TCEFORM.tt_content (and data processors in the TypoScript case). For example, configuring a linkHandler for the element, which requires both TypoScript and TSconfig.
Therefore, it would likely be beneficial if both aspects—TSconfig and TypoScript—could be fully configurable via page.tsconfig and setup.typoscript files located directly in the element's directory.
The text was updated successfully, but these errors were encountered: