Bug #87068

Use BackendUtility::getPagesTSconfig in TSFE when getting tsconfig

Added by Soren Malling 10 months ago. Updated 5 months ago.

Status:
Accepted
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-12-04
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Inside the TypoScriptFrontendController the method getPagesTSconfig is used to get the tsconfig from page records. Both via the TSconfig fields but also "included" tsconfig.

The method consist of the same code as BackendUtility::getRawPagesTSconfig (which is called by getPagesTSconfig) - the main difference is, that the frontend method doesn't call emit the signal GetPagesTSconfigPreIncludeSignal to have extensions auto include. So, this gives a different functionality from backend to frontend.

A usecase is inclusion of gridelements layouts. This is used in the frontend for rendering. But when TSFE gets the tsconfig, the signal is not emitted and the tsconfig is not being filled with the layout configuration like it does in the backend


Related issues

Related to Grid Elements (former official tracker) - now moved to Gitlab! - Bug #85627: Usage of BackendUtility::getPagesTSconfig() throws Error without BE-User Resolved 2018-07-24

History

#1 Updated by Jo Hasenau 5 months ago

  • Status changed from New to Accepted
  • Priority changed from Should have to Must have

Since this causes a breaking change between backend and frontend, IMHO that's a must have.

Today someone who had problems using themes with themes_gridelements confirmed that there are no layouts available in the frontend, while they still are in the backend.
So if we are using the same methods here, we have to make sure the corresponding slots are available too.

#2 Updated by Jo Hasenau 5 months ago

  • Related to Bug #85627: Usage of BackendUtility::getPagesTSconfig() throws Error without BE-User added

Also available in: Atom PDF