1

I’m migrating an Extbase content element to a FLUIDTEMPLATE cObj CE with dataprocessors. One problem I step into are Flexform + TypoScript settings. With Extbase I got a merged settings array of TypoScript and Flexform, with FLUIDTEMPLATE I just get the TypoScript.

I use Flexform and TypoScript settings e.g. to configure a slider:

<div class="slider" data-slick='{settings.slider.slick -> e:format.json.encode()}'>
t3easy
  • 41
  • 5
  • You can write a custom implementation of the `TYPO3\CMS\Frontend\ContentObject\DataProcessorInterface` and use it in your fluidcontent dataprocessor config like `10 = MyNamespace\DataProcessing\FlexformProcessor`. Inside the processor you can easily read and convert your flexform using the cObj-Object and `GeneralUtility::xml2array`. – Fabian S. Nov 08 '17 at 09:49
  • 1
    Example FlexFormProcessor: https://github.com/t3kit/t3kit_extension_tools/blob/master/Classes/DataProcessing/FlexFormProcessor.php – stmllr Nov 08 '17 at 11:20
  • Thank you! I'll have a look. – t3easy Nov 08 '17 at 12:25

1 Answers1

3

I checked the example provided by stmllr and made some changes that makes it act like the Extbase FrontendConfigurationManager https://gist.github.com/t3easy/22bdcf7189e0dce76e246a581790e4a4

Main change is, that just FlexForm prefixed with settings. are merged with TypoScript settings. And that I use ArrayUtility::mergeRecursiveWithOverrule. Hope that helps others to migrate.

t3easy
  • 41
  • 5