Access TypoScript in an extension 

Extbase controllers 

In Extbase controllers, Flexform settings and TypoScript settings will be merged together. If settings exists in both, the Flexform takes precedence and overrides the TypoScript setting. Note that both Flexform and TypoScript settings must use the convention of preceding the setting with settings. (for example, settings.threshold ).

Extbase offers some advantages: Some things work automatically out-of-the-box. However, you must stick to the Extbase conventions ("conventions over configuration").

In order to access TypoScript settings from an Extbase controller.

1. Use the convention of defining your TypoScript settings in settings

   EXT:my_extension/Configuration/TypoScript/setup.typoscript

   plugin.tx_myextension {
      view {
         # view settings
      }
   
      settings {
         key1 = value1
         key2 = value2
      }
   }

   Copied!

2. Access them via $this->settings

   For example, in your controller:

   $myvalue1 = $this->settings['key1'] ?? 'default';

   Copied!

Fluid 

If Extbase controllers are used, $this->settings is automatically passed to the Fluid template. Allowing you to access settings like this:

{settings.key1}

Without Extbase, a template rendered by the FLUIDTEMPLATE content object receives its settings from the settings property of that content object.

Reading frontend TypoScript from the PSR-7 request 

Any class that can reach the PSR-7 request — a content object, a middleware, an event listener — reads the parsed frontend TypoScript from the frontend.typoscript request attribute:

$fullTypoScript = $request->getAttribute('frontend.typoscript')
    ->getSetupArray();

Reading page TSconfig 

Page TSconfig is backend TypoScript and therefore not part of the frontend request. It is read for a single page with BackendUtility::getPagesTSconfig(), which returns the parsed TypoScript as an array.