ExtensionUtility::configurePlugin doesn't set typoscript
Upgrading to 6.2 beta 1 I've experienced that
TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin -> \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTypoScript doesn't register/writes the typoscript to the TypoScript Object Browser.
It writes it very well to $GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_' . $type . '.']
This seems to be a issue for Extbase only extension as EXT:gridelements got it's typoscript written as it used to
#4 Updated by Daniel Siepmann about 6 years ago
Adding a line to add it to the static typoscript FILE will work:
$GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_' . $type . '.']['cssstyledcontent/static/v4.6/'] .= $content;
That's not a fix, but workaround where you've to change the core.
I try to figure out what's the problem.
A better way, working for me, is to edit em_conf of your extension and add css_styled_content as depends.
Hope the bug will be solved soon, so we don't have to add the core extension as dependency.
#7 Updated by Daniel Siepmann about 5 years ago
As mentioned in slack, my opinion would be to add css_styled_content as suggested into ext_emconf of extbase. As css_styled_content is just one way to display content of TYPO3, and extbase supports this way, it is no dependency.
We just need to take care, whether PackageStates.php will follow the suggestions as it follows the dependencies.