constants¶

Migration¶

One possible solution is to switch to TypoScript constants / settings instead for simple cases.

A simple example usage before:

TypoScript setup:

constants.EMAIL = mail@example.com
page = PAGE
page.10 = TEXT
page.10.value = Write an email to ###EMAIL###
page.10.parseFunc.constants = 1

Switching to a TypoScript constant / setting:

TypoScript constants / settings:

myEmail = mail@example.com

TypoScript setup:

page = PAGE
page.10 = TEXT
page.10.value = Write an email to {$myEmail}

The main usage of this feature has been a "magic" substitution within lib.parseFunc_RTE:

When tt_content rich-text editor (RTE) content elements contain such substitution strings, they are replaced by parseFunc accordingly. For instance, a tt_content RTE element with the content Send an email to ###EMAIL### would substitute to Send an email to email@example.org if the top-level setup constants object has been set up.

This substitution relies on the the fact that editors actively know about and use this construct: If only one content element did not prepare for this - since an editor forgot or have not been trained about it, changing such a constant on TypoScript level would still lead to faulty frontend output, rendering the entire substitution approach useless.

In case instances still rely on this magic substitution principle, and made sure all editors always know and follow this approach, instances can use the userFunc property of parseFunc to re-implement the functionality:

Basically by copying the deprecated code to an own class and registering the userFunc in lib.parseFunc_RTE.