Project

General

Profile

Actions

Task #55942

closed

More robust way of appending TypoScript to contentrendering templates

Added by Benni Mack almost 11 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Frontend
Target version:
Start date:
2014-02-12
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

If an extension used static content ID 43 (content default),
it also added itself (during each runtime of ext_localconf.php)
to all available content blocks.
This is now more confusing as the package manager
resolves the ordering of extensions and now,
CSS Styled Content gets loaded after felogin and
indexed_search.

To resolve this problem completely, the additional
TypoScript for each "contentRenderingTemplate",
a TS template that provides default content renderings,
is added to one global default TypoScript and is only
merged at the TemplateService class.

Therefore the extension loading ordering
does not matter anymore.


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #56570: No rendering definition for CE / no list for plugins if csc is includes with INCLUDE_TYPOSCRIPTClosed2014-03-05

Actions
Related to TYPO3 Core - Bug #59318: Loading css_styled_content TS using INCLUDE_TYPOSCRIPT doesn't include defaultContentRenderingClosedMarc Bastian Heinrichs2014-06-03

Actions
Related to TYPO3 Core - Bug #67116: Plugin templates are always loaded twice!?ClosedMarkus Klein2015-05-23

Actions
Actions

Also available in: Atom PDF