TYPO3 Core

"I also do not really understand, what a real usecase for this feature would actually be."

e.g. an editor has no BE web-menu "Template" but he has the field page-TSConfig!
Normally this should be reaseon enough!?

I use it for image-description for images out of page resources that will be shown as a slider with jQuery.

An editor uploads two images e.g. into the page resources and writes into the page TSConfig:

TSFE.constants.myConstant1 = This is image 1
TSFE.constants.myConstant2 = This is image 2

TSFE.constants.xxx still do NOT work without an Ext.-Template. :-(
TYPO3 version 6.1.5

Note: We need to take a look on the performance implication if we walk through the rootline and have the TS parser run through potentially a LOT of TSConfig.

This issue seems still present in 9.5.2-dev (latest master)

Minimal test setup:

1) In your homepage with the main TS Template write:

page.11=TEXT
page.11.value = {$myConstant}
page.11.wrap=<h1>|</h1>

2) Create a page and write in TS Config field (resources tab):

TSFE.constants.myConstant = HELLO WORLD!

3) Save and preview

Result:¶

the constant is not replace and in frontend you will see:

<h1>{$myConstant}</h1>

4) Now add an EXT TypoScript Template in the same page; save and preview

Result:¶

the constant is now used:

<h1>HELLO WORLD!</h1>

This issue seems is present on 10.0.0-dev (latest master) - tested with the same procedure on my comment 12