[TYPO3-dev] ext_typoscript_setup.txt

[Elmar Hinz]

Hi Ernesto,

Elmar Hinz wrote:
> Ernesto Baschny [cron IT] wrote:
>> Hm, I am not sure what you mean with "core hack"? I don't think anything
>> has changed, and still everything works "as usual" (meaning all
>> extensions are still working as they were in previous versions).
>>
> 
> I try to relocate the "core hack". If everything works like usual this
> means IMHO that you can't replace css_styled_content with another rendering
> setup like you imagine, because it would have the wrong id. All extensions
> work.  But they only work with css_styled_content or "content (default)",
> but with nothing else.
> 

Hier it is:

<http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/browser/typo3/TYPO3core/trunk/t3lib/class.t3lib_extmgm.php?rev=4768>

Line: 872 - 874


872 if ($afterStaticUid==43)    {    // If 'content (default)' is targeted,
also add to other 'content rendering templates', eg. css_styled_content
873
$TYPO3_CONF_VARS['FE']['defaultTypoScript_'.$type.'.']['cssstyledcontent/static/'].=$content;
874 }

The function is short and easy to XCLASS.

To get rid of the XCASS a little change would be nice. Just replace
'cssstyledcontent/static/' with a global variable and you really can use
any rendering setup.

$TYPO3_CONF_VARS['FE']['defaultTypoScript_'.$type.'.']['cssstyledcontent/static/'].=$content;

$TYPO3_CONF_VARS['FE']['defaultTypoScript_'.$type.'.'][$SomeGlobalVariabel].=$content;


Regards

Elmar