Feature #47036
closed
PAGE_TSCONFIG_ in displayCond
0%
Description
Actualy we can't use PAGE_TSCONFIG_ in displayCond. It would be a good feature.
'displayCond' => 'FIELD:field:=:###PAGE_TSCONFIG_ID###'
Updated by Nicole Cordes over 11 years ago
- TYPO3 Version changed from 6.0 to 6.2
As this is a feature request it can only be included in newer TYPO3 versions. As there is the feature freeze for 6.1 already the lowest version would be TYPO3 6.2
Updated by Nicolas Forgeot over 11 years ago
Thank for your answer. I will use an second field of type user : "isFieldCondition" with tsConfig. In main field : 'displayCond' => 'FIELD:isFieldCondition:=:1'.
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.4 (Backend)
- Is Regression set to No
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Mathias Schreiber about 9 years ago
- Tracker changed from Bug to Feature
- Target version changed from 7 LTS to 8 LTS
Updated by Christian Kuhn almost 8 years ago
- Status changed from New to Rejected
Uhm ... the display condition stuff is imho already much too complex and capable of doing a LOT of stuff already. Combining that with pageTS makes it even more complex. Imho, we really should NOT implement such a feature by default, at least not at the moment and only if lots of people are in deep need of that.
It is also possible to hide certain fields by pageTs directly, maybe that is enough in you use case.
If you really really need that for a project, please substitute the EvaluateDisplayConditions data provider with an own version to implement that. The data you need will be in $result. Also have a look at the display condition parser rewrite from patch https://review.typo3.org/#/c/50879/.