Bug #98552
closed
Content not rendered in frontend in v12.0
100%
Description
Without activating the option "Clear setup" in the sys_template record of the root page, no content elements are displayed in frontend.
Steps:
- Install TYPO3 v12.0
- In the setup tool choose the option "Create empty start page"
- Create in backend a content element on the start page
- Look at the frontend output: no content element is displayed
- Activate "Clear setup" in sys_template record
- Look at the frontend output: content element is displayed
Updated by Chris Müller about 2 years ago
- Subject changed from Content element not rendered in frontend in v12.0 to Content not rendered in frontend in v12.0
Updated by Riccardo De Contardi about 2 years ago
I've been able to reproduce the problem with a very basic TypoScript setup like:
page = PAGE
page.5 = TEXT
page.5 {
data = page:title
wrap = <h1>|</h1>
}
page.100 = CONTENT
page.100 {
table = tt_content
select {
orderBy = sorting
where = {#colPos}=0
}
}
The page.5 object is rendered, while page.100 is not
Updated by Georg Ringer about 2 years ago
- Assignee set to Christian Kuhn
- Target version set to 12.1
Updated by Gerrit Code Review about 2 years ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76082
Updated by Christian Kuhn about 2 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 93e3b68cf0c0d9baccf442e8105de1f385e31f51.
Updated by Chris Müller about 2 years ago
- Has duplicate Bug #98623: Set "clear setup" option when creating a new page in the install tool added
Updated by
Updated by Christian Kuhn almost 2 years ago
- Related to Bug #99331: Dynamically set 'clear' TypoScript flag added
Updated by Christian Kuhn almost 2 years ago
- Related to Feature #97816: New TypoScript parser added