Bug #52946

ExtensionUtility::configurePlugin doesn't set typoscript

Added by Soren Malling almost 6 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2013-10-18
Due date:
% Done:

0%

TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

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


Related issues

Related to TYPO3 Core - Bug #59318: Loading css_styled_content TS using INCLUDE_TYPOSCRIPT doesn't include defaultContentRendering Closed 2014-06-03

History

#1 Updated by Soren Malling almost 6 years ago

Title is wrong, is was TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin and not the registerPlugin function

#2 Updated by Markus Klein almost 6 years ago

  • Subject changed from TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin doesn't set typoscript to ExtensionUtility::configurePlugin doesn't set typoscript

#3 Updated by Jo Hasenau almost 6 years ago

FYI: Gridelements does not use addTypoScript at all, but uses addStaticFile instead.

I think the difference is, that you have to include the static file then, while addTypoScript would insert the TS-code directly.

#4 Updated by Daniel Siepmann over 5 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.

#5 Updated by Mathias Schreiber over 4 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

Hey Daniel,

any progress here?

#6 Updated by Daniel Siepmann over 4 years ago

No sorry. I went on to other issues.

#7 Updated by Daniel Siepmann over 4 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.

#8 Updated by Alexander Opitz about 4 years ago

  • Status changed from Needs Feedback to New

#9 Updated by Benni Mack 9 months ago

  • Status changed from New to Needs Feedback
  • Assignee deleted (Mathias Schreiber)

Hi Soren,

can you check if this issue still exists now with TYPO3 v8 and TYPO3 v9 and fluid_styled_content?

#10 Updated by Soren Malling 9 months ago

This issue can be closed :)

#11 Updated by Riccardo De Contardi 9 months ago

  • Status changed from Needs Feedback to Closed

@Soren Malling Hi and thank you for your kind and quick answer;

Closed in agreement with the reporter.

Thanks again

R.

Also available in: Atom PDF