PageContentFetchingProcessor implements DataProcessorInterface

Read onlyYes

All-in-one data processor that loads all tt_content records from the current page layout into the template with a given identifier for each colPos, also respecting slideMode or collect options based on the page layouts content columns.

Use "as" for the target variable where the fetched content elements will be provided. If empty, "content" is used.

Example TypoScript configuration:

page = PAGE page { 10 = PAGEVIEW 10 { paths.10 = EXT:my_site_package/Resources/Private/Templates/ dataProcessing { 10 = page-content 10.as = myContent } } }

which fetches all content elements for the current page and provides them as "myContent".

Table of Contents

Interfaces

DataProcessorInterface
Interface for data processor classes processing data from ContentObjectRenderer, used e.g. with the FLUIDTEMPLATE content object

Properties

$eventDispatcher  : EventDispatcherInterface
$pageLayoutResolver  : PageLayoutResolver
$recordCollector  : RecordCollector

Methods

__construct()  : mixed
process()  : array<string|int, mixed>
Process content object data

Properties

$eventDispatcher

protected EventDispatcherInterface $eventDispatcher

Methods

process()

Process content object data

public process(ContentObjectRenderer $cObj, array<string|int, mixed> $contentObjectConfiguration, array<string|int, mixed> $processorConfiguration, array<string|int, mixed> $processedData) : array<string|int, mixed>
Parameters
$cObj : ContentObjectRenderer

The data of the content element or page

$contentObjectConfiguration : array<string|int, mixed>

The configuration of Content Object

$processorConfiguration : array<string|int, mixed>

The configuration of this processor

$processedData : array<string|int, mixed>

Key/value store of processed data (e.g. to be passed to a Fluid View)

Return values
array<string|int, mixed>

the processed data as key/value store


        
On this page

Search results