---
title: "How To"
manual: "Grid Elements"
version: "main"
permalink: "https://docs.typo3.org/permalink/gridelementsteam/gridelements:dataprocessinghowto@main"
source: "Chapters/Rendering/DataProcessing/HowTo/Index.rst"
rendered: "2026-11-04T14:20:48+00:00"
---

# How To {#dataprocessinghowto}

This guide outlines the configuration of the `GridChildrenProcessor`, its options, and examples of corresponding templates and partials for rendering grid-based layouts in TYPO3.

## Recommended approach vs. legacy path {#recommended-approach-vs-legacy-path}

The `GridChildrenProcessor` represents the recommended, Fluid-based approach to handling grid layouts in TYPO3, offering significant advantages over the deprecated legacy path built on the `Gridelements` plugin. See [Rendering Architecture](https://docs.typo3.org/permalink/gridelementsteam/gridelements:renderingarchitecture@main) for how the two relate.

**Legacy path (deprecated, not recommended for new projects):**
The original Grid Elements implementation relied on the `Gridelements->main` userFunc in TypoScript, which processed grid children internally and rendered them using pre-defined TypoScript objects (COA, TEMPLATE). This method required extensive TypoScript configuration for customization and made it difficult to separate content structure from presentation.

**Recommended approach with GridChildrenProcessor:**
The DataProcessor approach leverages TYPO3's ContentObjectRenderer data processing capabilities to:

-   Separate data gathering from rendering logic
-   Allow full Fluid template control over the grid structure
-   Provide specific rendering options per grid layout type
-   Enable recursive processing of nested grids with clean template code
-   Offer greater flexibility through configuration options like `respectColumns` and `respectRows`
-   Integrate seamlessly with other TYPO3 data processors

This approach significantly improves maintainability and template reusability, and follows TYPO3's current best practices for content rendering.

## Example Configuration {#example-configuration}

Below is an example `GridChildrenProcessor` configuration:

```typoscript
lib.gridelements {
    templateName = GridElement
    templateName.override.field = tx_gridelements_backend_layout
    templateRootPaths {
        1 = EXT:gridelements/Resources/Private/Templates/
    }

    partialRootPaths {
        1 = EXT:gridelements/Resources/Private/Partials/
    }

    dataProcessing {
        10 = GridElementsTeam\Gridelements\DataProcessing\GridChildrenProcessor
        10 {
            default {
                as = children
                options {
                    sortingDirection = asc
                    sortingField = sorting
                    recursive = 0
                    resolveFlexFormData = 1
                    resolveChildFlexFormData = 1
                    resolveBackendLayout = 1
                    respectColumns = 1
                    respectRows = 1
                }
            }
        }
    }
}
```

---

## Templates and Partials {#templates-and-partials}

The templates and partials used with `GridChildrenProcessor` extend TYPO3's grid-based rendering functionality. Samples are provided below for each template and partial used in the configuration.
Those samples are provided by Grid Elements out of the box, but you can of course still create your own templates with fewer conditions, if your layouts are strictly bound to a certain configuration.
Just add those settings to the TypoScript template based on your Grid Elements backend layouts and configure them to your needs.

```typoscript
10 = GridElementsTeam\Gridelements\DataProcessing\GridChildrenProcessor
10 {
    default {
        [...]
    }
    myLayout1 {  # Custom key for this layout
        as = children
        options {
            sortingField = title  # Sort child elements alphabetically by their title
            sortingDirection = desc  # Change sorting direction to descending
            recursive = 0  # Do not pre-fetch a nested container's own children in this pass
            resolveFlexFormData = 0  # Keep original FlexForm XML without conversion
            resolveBackendLayout = 0  # Disable resolution of backend layouts
            respectColumns = 0  # Disable column grouping
            respectRows = 0  # Also disable row grouping; respectRows defaults to 1 and row handling requires column handling, so both must be off for a genuinely flat list
        }
    }
    myLayout2 {  # Custom key for this layout
        as = somethingElse  # use a different key to deal with your child elements
        options {
            recursive = 1  # Pre-fetch one additional level of nested container children in this pass
            respectColumns = 1  # Group children by their column value
            respectRows = 0  # Skip grouping by rows, e.g. with a single row configuration
        }
    }
}
```

`recursive` only changes how many levels of children this processing
pass pre-fetches in one go. It is not a structural depth limit;
nesting itself is unconditional and unaffected by this option, see
[Nesting](https://docs.typo3.org/permalink/gridelementsteam/gridelements:nesting@main) for the full distinction between structural nesting,
this option, and the Fluid template recursion described below.

### **Template: GridElement.html** {#template-gridelement-html}

This is the main entry template for rendering the grid layout.

```html
<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" data-namespace-typo3-fluid="true">
    <f:layout name="Default"/>
    <f:section name="Main">
        <f:render partial="Container" arguments="{_all}"/>
    </f:section>
</html>
```

### **Partial: Container.html** {#partial-container-html}

The `Container` partial is the central rendering controller. It uses the switches `respectColumns` and `respectRows` to dynamically determine whether to render content hierarchically by rows, columns, or as a flat list of child elements.

If **\`respectColumns\`** is enabled:
\- Child elements are grouped into columns according to their `tx_gridelements_columns` values.
\- Each column group is rendered by the `Columns` partial.

If **\`respectRows\`** is also enabled:
\- Child elements are first grouped into rows based on the layout configuration.
\- Within each row, child elements are further grouped into their respective columns, using the `Rows` and `Columns` partials.

If neither switch is enabled:
\- All child elements are rendered as a flat list using the `Child` partial.

```html
<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" data-namespace-typo3-fluid="true">
    <div class="grid-container grid-container-{data.tx_gridelements_backend_layout}">
        <f:if condition="{options.respectColumns}">
            <f:then>
                <f:if condition="{options.respectRows}">
                    <f:then>
                        <f:render partial="Rows" arguments="{data: data, rows: children, options: options, settings: settings}"/>
                    </f:then>
                    <f:else>
                        <f:render partial="Columns" arguments="{data: data, columns: children, options: options, settings: settings}"/>
                    </f:else>
                </f:if>
            </f:then>
            <f:else>
                <f:if condition="{children}">
                    <f:for each="{children}" as="child">
                        <f:render partial="Child" arguments="{data: child.data, children: child.children, options: options, settings: settings}"/>
                    </f:for>
                </f:if>
            </f:else>
        </f:if>
    </div>
</html>
```

### **Partial: Rows.html** {#partial-rows-html}

This partial organizes child elements into rows and delegates further rendering to the `Columns` partial if `respectColumns` is enabled.

```html
<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" data-namespace-typo3-fluid="true">
    <f:if condition="{rows}">
        <f:for each="{rows}" as="columns" key="rowNumber">
            <div id="c{data.uid}-{rowNumber}" class="grid-row grid-row-{rowNumber}">
                <f:render partial="Columns" arguments="{data: data, columns: columns, options: options, settings: settings}"/>
            </div>
        </f:for>
    </f:if>
</html>
```

### **Partial: Columns.html** {#partial-columns-html}

Handles rendering of columns by grouping child elements into their respective `tx_gridelements_columns` values. Child elements within each column are delegated to the `Child` partial.

```html
<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" data-namespace-typo3-fluid="true">
    <f:if condition="{columns}">
        <f:for each="{columns}" as="column" key="columnNumber">
            <div id="c{data.uid}-{columnNumber}" class="grid-column grid-column-{columnNumber}">
                <f:for each="{column}" as="child">
                    <f:render partial="Child" arguments="{data: child.data, children: child.children, options: options, settings: settings}"/>
                </f:for>
            </div>
        </f:for>
    </f:if>
</html>
```

### **Partial: Child.html** {#partial-child-html}

Renders individual child elements. If the child element itself is a container, this partial recursively calls the `Container` partial to render its children.

```html
<html xmlns:f="http://typo3.org/ns/TYPO3/CMS/Fluid/ViewHelpers" data-namespace-typo3-fluid="true">
    <f:if condition="{children}">
        <f:then>
            <a id="c{data.uid}"></a>
            <f:if condition="{data._LOCALIZED_UID}">
                <a id="c{data._LOCALIZED_UID}"></a>
            </f:if>
            <f:render partial="Container" arguments="{_all}" optional="true"/>
        </f:then>
        <f:else>
            <f:if condition="{data.CType}">
                <f:cObject typoscriptObjectPath="tt_content" data="{data}" table="tt_content" />
            </f:if>
        </f:else>
    </f:if>
</html>
```

This is the Fluid template recursion described in [Nesting](https://docs.typo3.org/permalink/gridelementsteam/gridelements:nesting@main):
when pre-fetched `children` data is present, `Child.html` renders
straight back into the `Container` partial; otherwise the child is
rendered through TYPO3's standard `tt_content` CASE dispatch on `CType`,
which re-enters this same processing chain from scratch if that child
is itself a Grid Element. Either way, the structure renders completely
regardless of how deep it nests.

---

## Advantages {#advantages}

-   **Flexible Layout Management:** Powerful control over rendering child elements as rows, columns, or lists. Adjust processing dynamically with `respectRows` and `respectColumns`.
-   **Dynamic Nesting:** Nested grid structures render at any depth without extra configuration, see [Nesting](https://docs.typo3.org/permalink/gridelementsteam/gridelements:nesting@main). The `recursive` option only controls how many of those levels this processing pass pre-fetches in one go.
-   **Adaptable Templates:** Templates and partials reflect layout variations, allowing developers to customize rendering for unique use cases.
-   **Streamlined Processing:** Integrates with TYPO3's `dataProcessing` to combine FlexForm data, sorting, and grouping in a single pipeline.
