---
title: "Extension Points"
manual: "Grid Elements"
version: "main"
permalink: "https://docs.typo3.org/permalink/gridelementsteam/gridelements:developerreferenceextensionpoints@main"
source: "Chapters/DeveloperReference/ExtensionPoints/Index.rst"
rendered: "2026-11-04T14:20:48+00:00"
---

# Extension Points {#developerreferenceextensionpoints}

Grid Elements integrates with TYPO3's backend and DataHandler almost
entirely through PSR-14 events, all registered in
`Configuration/Services.yaml`. A handful of legacy `$GLOBALS` hooks
remain in use where Core does not yet offer an event for the relevant
operation. XCLASSing is exceptional: exactly one core class is
XCLASSed, and only when a project explicitly opts in. This page lists
the actual current mechanisms by class and event name, and calls out
the one place where an older registration has become dead code
rather than describing it as if it still ran.

## PSR-14 events Grid Elements listens to {#psr-14-events-grid-elements-listens-to}

| Core event | Listener | Purpose |
| --- | --- | --- |
| `AfterTcaCompilationEvent` | `EventListener\ExtTablesInclusionPostProcessing` | Registers Grid Elements' Page Module (Web > Page on TYPO3 13, Content > Layout on TYPO3 14) preview renderers (`GridelementsPreviewRenderer`, `ShortcutPreviewRenderer`) into the compiled TCA. |
| `BeforeFlexFormDataStructureIdentifierInitializedEvent` | `EventListener\BeforeFlexFormDataStructureIdentifierInitializedListener` | Resolves the FlexForm data-structure identifier for `gridelements_pi1` containers. |
| `BeforeFlexFormDataStructureParsedEvent` | `EventListener\BeforeFlexFormDataStructureParsedListener` | Supplies the default Grid Elements FlexForm data structure (or a project-defined `flexformDS`) for that identifier. |
| `TYPO3\CMS\Backend\View\Event\ModifyDatabaseQueryForRecordListingEvent` | `EventListener\ModifyDatabaseQueryForRecordListingListener` | Excludes grid children (`colPos = -1`) from the base query of the List module (Web > List on TYPO3 13, Content > Records on TYPO3 14), see [List Module Integration](https://docs.typo3.org/permalink/gridelementsteam/gridelements:developerreferencelistmoduleintegration@main). |
| `TYPO3\CMS\Backend\View\Event\ManipulateBackendLayoutColPosConfigurationForPageEvent` (TYPO3 14 only; declared `@internal` by TYPO3 Core) | `EventListener\ManipulateBackendLayoutColPosConfigurationListener` | Merges the `allowed.CType`/`disallowed.CType` rules of the page's Backend Layout into TYPO3 Core's `allowedContentTypes`/ `disallowedContentTypes` column configuration. While the preview of a grid child is rendered, it supplies the configuration of the child's container column instead, see [Restrictions, Validation & Permissions](https://docs.typo3.org/permalink/gridelementsteam/gridelements:restrictions@main). The event does not exist on TYPO3 13, so the listener is not called there. |
| `TYPO3\CMS\Backend\Controller\Event\ModifyNewContentElementWizardItemsEvent` | `EventListener\ModifyNewContentElementWizardItemsListener` | Filters the New Content Element Wizard's item list against the target cell's `allowed`/`disallowed` restrictions, see [Restrictions, Validation & Permissions](https://docs.typo3.org/permalink/gridelementsteam/gridelements:restrictions@main). |
| `TYPO3\CMS\Backend\View\Event\IsContentUsedOnPageLayoutEvent` | `EventListener\IsContentUsedOnPageLayoutListener` | Marks a grid child (`colPos = -1` with a set `tx_gridelements_container`) as used. This is the current, functioning replacement for the `record_is_used` hook, which TYPO3 Core removed in TYPO3 12 (Breaking-98375). |
| `TYPO3\CMS\Backend\Controller\Event\AfterBackendPageRenderEvent` | `EventListener\AfterBackendPageRendererEventListener` | Injects Grid Elements' JavaScript language labels into the backend page. |
| `TYPO3\CMS\Backend\Controller\Event\ModifyPageLayoutContentEvent` | `EventListener\ModifyPageLayoutContentEventListener` | Exposes clipboard paste settings and loads the Drag-In Wizard JavaScript module in the Page Module, see [Drag-In Wizard](https://docs.typo3.org/permalink/gridelementsteam/gridelements:editorguidedraginwizard@main). |

## Grid Elements' own event {#grid-elements-own-event}

`GridElementsTeam\Gridelements\Event\ModifyRecordListElementDataEvent`
is dispatched by Grid Elements itself, from the List module XCLASS
described below, once per row, and implements
`Psr\EventDispatcher\StoppableEventInterface`. Its own listener,
`EventListener\ModifyRecordListElementDataListener`, attaches the
container/child markers (`_CONTAINER_COLUMNS_`, `_EXPANDABLE_`,
`_EXPAND_ID_`, `_EXPAND_TABLE_`, `_LEVEL_`, `_CHILDREN_`) the
List module rendering needs, but it is a regular PSR-14 event on the
event bus like any other: another extension can listen to it too, for
example to add its own markers to the same row data.

## TYPO3 hooks still in use {#typo3-hooks-still-in-use}

These are legacy `$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']` hook
registrations, kept because Core has not replaced them with PSR-14
events for the operations they cover.

| Hook point | Class | Purpose |
| --- | --- | --- |
| `t3lib/class.t3lib_tcemain.php` `processDatamapClass` | `Hooks\DataHandler` | Field-array preprocessing and post-save consistency work, see [Parent-Child Relations and IRRE](https://docs.typo3.org/permalink/gridelementsteam/gridelements:parentchildirre@main), plus restriction enforcement, see [Restrictions, Validation & Permissions](https://docs.typo3.org/permalink/gridelementsteam/gridelements:restrictions@main). |
| `t3lib/class.t3lib_tcemain.php` `processCmdmapClass` | `Hooks\DataHandler` | Copy/move command handling ("Paste as Reference", child-count maintenance, cycle protection) and restriction enforcement for commands, see [Parent-Child Relations and IRRE](https://docs.typo3.org/permalink/gridelementsteam/gridelements:parentchildirre@main) and [Restrictions, Validation & Permissions](https://docs.typo3.org/permalink/gridelementsteam/gridelements:restrictions@main). |
| `t3lib/class.t3lib_tcemain.php` `moveRecordClass` | `Hooks\DataHandler` | Registered against the same class, but `Hooks\DataHandler` does not currently implement a `moveRecord()` method, so this particular registration has no effect. Move-time consistency is instead handled through `processCmdmap()` and `processCmdmap_beforeStart()`, which do run on a drag-and-drop or cut/paste move. |

One further hook registration exists in `ext_tables.php` but no
longer runs, because the TYPO3 Core hook point it targets has been
removed in the versions this branch supports (`^13.4.7 || ^14.3`):

-   **\`\`typo3/class.db_list_extra.inc\`\` \`\`actions\`\`**
    (`Hooks\DatabaseRecordList`, registered only when
    `nestingInListModule` is enabled) targets a hook point Core no
    longer dispatches either. Only one method on that class,
    `contentCollapseIcon()`, remains functional, and it is reached by
    a direct call from the XCLASS below, not through this hook point,
    see [List Module Integration](https://docs.typo3.org/permalink/gridelementsteam/gridelements:developerreferencelistmoduleintegration@main).

## XCLASS (exceptional) {#xclass-exceptional}

Grid Elements XCLASSes exactly one Core class,
`TYPO3\CMS\Backend\RecordList\DatabaseRecordList`, and only when a
project has explicitly enabled the `nestingInListModule` extension
configuration option. Two implementations are registered depending on
the running Core version, since the parent class's own API differs
between them:

| TYPO3 | Class | Notes |
| --- | --- | --- |
| 14 | `Xclass\DatabaseRecordList` | Marked `@internal` in its own docblock: it extends a Core class that is explicitly not part of Core's public API, and can change in a minor release. Do not XCLASS it further; extend Grid Elements' own event (above) instead where possible. |
| 13 | `Xclass\DatabaseRecordList13` | Same role, adapted to the TYPO3 13 version of the parent class. |

See [List Module Integration](https://docs.typo3.org/permalink/gridelementsteam/gridelements:developerreferencelistmoduleintegration@main) for what this
XCLASS actually renders and why an event alone was not enough for it.

## Other Core registration points {#other-core-registration-points}

A few further integrations use Core's own configuration-array
registries rather than a hook or an event. They are listed here for
completeness, since each is a place a project could otherwise assume
Grid Elements uses a hook where it does not:

-   **FormEngine node registry**
    (`$GLOBALS['TYPO3_CONF_VARS']['SYS']['formEngine']['nodeRegistry']`)
    registers `Wizard\GridelementsBackendLayoutWizardElement` (TYPO3
    13 and 14) as the `belayoutwizard` FormEngine node, the Grid Wizard's
    backend rendering, see [Grid Wizard](https://docs.typo3.org/permalink/gridelementsteam/gridelements:gridwizard@main).
-   **Context menu item providers**
    (`$GLOBALS['TYPO3_CONF_VARS']['BE']['ContextMenu']['ItemProviders']`)
    registers `ContextMenu\ItemProvider` for the "Paste as Reference"
    action, see [References](https://docs.typo3.org/permalink/gridelementsteam/gridelements:editorguidereferences@main).
-   **Scheduler task types and console commands** register the data
    consistency tools described in full at [Data Consistency Tools](https://docs.typo3.org/permalink/gridelementsteam/gridelements:dataconsistencytools@main).

For how these mechanisms compare to EXT:container's own hooks, events
and class-replacement overrides, and the technically meaningful sense
in which "Core-native" does and does not apply to either extension,
see [Grid Elements and EXT:container](https://docs.typo3.org/permalink/gridelementsteam/gridelements:gridelementsandcontainer@main).
