Project

General

Profile

Actions

Bug #55028

closed

Static TS must be available even when there is no page UID

Added by Claus Due over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
Start date:
2014-01-15
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

Commit ba2386e7305e0d6e64db5cc485bc38728728ad8e https://review.typo3.org/26675 must be reverted - it destroys Extbase operability under the following criteria:

  • Editing any record (pid is not set).
  • Using any BE module that does not use the page tree.

Before, Extbase would look for the first root template. Felix removed this behaviour completely, replacing it with a raw $_GET['id']. This should be considered a HUGE breaking change for any third-party Extbase extension that operates in the BE without using a page tree. As such, it should not be allowed in the LTS.

Core extensions are not broken by this simply because they abuse the ext_typoscript_setup.txt pattern to load (massive) amounts of TS that cannot be controlled.


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Task #54701: Cache global TypoScript template in backendClosedFelix Oertel2014-01-02

Actions
Related to TYPO3 Core - Task #54813: BackendConfigurationManager figures out wrong pidClosed2014-01-07

Actions
Related to TYPO3 Core - Task #86262: Deprecate FE TypoScript processing in BERejected2018-09-15

Actions
Actions #1

Updated by Anja Leichsenring over 10 years ago

Discussion goes here: http://forge.typo3.org/issues/54701
Please comment there.

Actions #2

Updated by Marc Bastian Heinrichs over 10 years ago

  • Category set to Extbase
  • Status changed from New to Closed
  • Target version set to 6.2.0

Patch is reverted.

Claus Due wrote:

Core extensions are not broken by this simply because they abuse the ext_typoscript_setup.txt pattern to load (massive) amounts of TS that cannot be controlled.

But you would even have the same with typoscript on pid 0. But this is another story and should be discussed somewhere else.

Actions #3

Updated by Christian Kuhn over 5 years ago

  • Related to Task #86262: Deprecate FE TypoScript processing in BE added
Actions

Also available in: Atom PDF