[TYPO3-dev] addPItoST43 broken under TYPO3 6.2beta1
Franz Holzinger
franz at ttproducts.de
Thu Nov 14 13:00:18 CET 2013
Hello,
the FE plugins of extensions are not inserted in the TYPO3 script of
tt_content.
tt_content.list.20.agency = < plugin.tx_agency
This should have been added. But it fails. The failure happens since the
upgrade from TYPO3 6.1 to 6.2 beta1.
Maybe this has to do with the bug #38698
http://forge.typo3.org/issues/38698 .
ExtensionManagementUtility.php: addPItoST43
Function addTypoScript does not add the setup line to tt_content because
$GLOBALS['TYPO3_CONF_VARS']['FE']['contentRenderingTemplates'] is empty.
if ($afterStaticUid) {
$GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_' . $type .
'.'][$afterStaticUid] .= $content;
// If 'content (default)' is targeted, also add to other 'content
rendering templates', eg. css_styled_content
if ($afterStaticUid == 43 &&
is_array($GLOBALS['TYPO3_CONF_VARS']['FE']['contentRenderingTemplates'])) {
foreach
($GLOBALS['TYPO3_CONF_VARS']['FE']['contentRenderingTemplates'] as
$templateName) {
$GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_' . $type .
'.'][$templateName] .= $content;
}
}
} else {
$GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_' . $type] .=
$content;
}
No global variable will be set.
This has the effect that the FE plugin is not called any more because
the tt_content.20.key with field list_type setup for the extension is
missing. Therefore the extension's PHP code is not called at all. The
TypoScript of the extension is still there.
What has been changed in TYPO3 6.2 beta1? It seems to have something to
do with contentRenderingTemplates.
- Franz
More information about the TYPO3-dev
mailing list