[TYPO3-bugs] open bug #19739

[Philipp Gampe]

Hi Benjamin Mack,

Benjamin Mack wrote:

> Hey Franz,
> 
> I really don't see this "required" for the core. This are the reasons why:
> 
> 1. If you need to ship custom TypoScript code based if an extension is
> loaded, this should be done in ext_localconf.php with certain
> conditions. Why? Adding a lot of TypoScript conditions (even shipped
> with an extension) leads to a lot of multiple caching, thus I'm against
> using TS condition a lot.

This condition is static as long as the list of extensions does not change. 
Therefore no more cache variants are created. The merge possibility of 
multiple cache variants does not create them in reality. Checking the list 
of extensions is a cheap operation, because the list of extensions is know 
at runtime anyway.

> 2. Checking for an extension should be done at ext_localconf.php time.
> E.g. A lightbox extension ships an adaption for tt_content and tt_news,
> adding TypoScript as static includes, for each extension. This is how
> most people do it these days, or with options in Constant Editor.

This is right, but requires PHP knowledge. Can you add this to the docs 
(e.g. core API)?

> 3. I have - seriously - quite some TS conditions that are great for our
> projects. But: I can register my own now, in a very nice way and ship it
> as an extension, which I do.

A user condition should work too as described here:
http://docs.typo3.org/typo3cms/TyposcriptSyntaxReference/TypoScriptParserApi/CustomConditions/Index.html

Note: Such information should be added to the issue before closing it.

Best regards
-- 
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – Active contributor TYPO3 CMS
TYPO3 .... inspiring people to share!