Bug #30097
Content must be renderable using a nodePath and a TypoScript object path
| Status: | Closed | Start date: | 2011-09-20 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
When rendering a nodePath, it would be cool if we could render it completely out-of-context. I.e. render just a single content element being part of a bigger page.
However, the current TypoScript does not yet support rendering a single content element depending on the current object path; so it could look like:
/.../somePage/someSection/text?typoscriptObjectPath=page.sections.someSection.text
Greets, Sebastian
Related issues
History
#1 Updated by Sebastian Kurfuerst over 3 years ago
- Status changed from New to Closed
closing because we use #31638 to track this feature.