Task #48363
Work Package #48275: TypoScript consistency
(maybe) implement declarative configuration per TYPO3CR Node
| Status: | New | Start date: | 2013-05-17 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
in the long run, we thought of having static, per-node configuration values which "shine through" to subnodes
is a good idea. Especially with the removal described in #48321, this feature might become more important.
Possible use cases are that editors can set teaser colors, mark site areas, ... -- all could influence the rendering
- That's somehow comparable to the "constants" in TypoScript of TYPO3 CMS
- they would be available in FlowQuery / eel, possibly through
${node.configuration.XYZ} - they would be merged recursively (maybe in a configurable manner)
alternatively, we can implement a FlowQuery Operation slide which can be used to get node properties, and if they do not exist on the current node, do the same on the parent node. That could "emulate" this behavior; and might even be more elegant than an extra "configuration" array.
Related issues
History
#1 Updated by Jacob Floyd about 2 years ago
Whether or not we have the configuration array, I would like the slide option. I used various slide extensions in TYPO3 CMS to get that feature because it gave me the simplest way to accomplish what I wanted. +1 for slide. I'm okay with having both slide and configuration, however.