Extension Points
Grid Elements integrates with TYPO3's backend and DataHandler almost
entirely through PSR-14 events, all registered in
Configuration/. 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
| Core event | Listener | Purpose |
|---|---|---|
After | Event | Registers Grid Elements' Page Module (Web > Page on TYPO3 13,
Content > Layout on TYPO3 14) preview renderers
(Gridelements, Shortcut)
into the compiled TCA. |
Before | Event | Resolves the FlexForm data-structure identifier for
gridelements_ containers. |
Before | Event | Supplies the default Grid Elements FlexForm data structure (or
a project-defined flexform) for that identifier. |
TYPO3\ | Event | Excludes grid children (col) from the base query of
the List module (Web > List on TYPO3 13, Content > Records on
TYPO3 14), see List Module Integration. |
TYPO3\
(TYPO3 14 only; declared @internal by TYPO3 Core) | Event | Merges the allowed./disallowed. rules of the
page's Backend Layout into TYPO3 Core's allowed/
disallowed 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. The
event does not exist on TYPO3 13, so the listener is not called
there. |
TYPO3\ | Event | Filters the New Content Element Wizard's item list against the
target cell's allowed/disallowed restrictions, see
Restrictions, Validation & Permissions. |
TYPO3\ | Event | Marks a grid child (col with a set
tx_) as used. This is the current,
functioning replacement for the record_ hook, which
TYPO3 Core removed in TYPO3 12 (Breaking-98375). |
TYPO3\ | Event | Injects Grid Elements' JavaScript language labels into the backend page. |
TYPO3\ | Event | Exposes clipboard paste settings and loads the Drag-In Wizard JavaScript module in the Page Module, see Drag-In Wizard. |
Grid Elements' own event
Grid
is dispatched by Grid Elements itself, from the List module XCLASS
described below, once per row, and implements
Psr\. Its own listener,
Event, attaches the
container/child markers (_CONTAINER_, _EXPANDABLE_,
_EXPAND_, _EXPAND_, _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
These are legacy $GLOBALS hook
registrations, kept because Core has not replaced them with PSR-14
events for the operations they cover.
| Hook point | Class | Purpose |
|---|---|---|
t3lib/ process | Hooks\ | Field-array preprocessing and post-save consistency work, see Parent-Child Relations and IRRE, plus restriction enforcement, see Restrictions, Validation & Permissions. |
t3lib/ process | Hooks\ | Copy/move command handling ("Paste as Reference", child-count maintenance, cycle protection) and restriction enforcement for commands, see Parent-Child Relations and IRRE and Restrictions, Validation & Permissions. |
t3lib/ move | Hooks\ | Registered against the same class, but Hooks\
does not currently implement a move method, so this
particular registration has no effect. Move-time consistency is
instead handled through process and
process, which do run on a
drag-and-drop or cut/paste move. |
One further hook registration exists in ext_ but no
longer runs, because the TYPO3 Core hook point it targets has been
removed in the versions this branch supports (^13.):
- ``typo3/class.db_list_extra.inc`` ``actions``
(
Hooks\, registered only whenDatabase Record List nestingis enabled) targets a hook point Core no longer dispatches either. Only one method on that class,In List Module content, remains functional, and it is reached by a direct call from the XCLASS below, not through this hook point, see List Module Integration.Collapse Icon ()
XCLASS (exceptional)
Grid Elements XCLASSes exactly one Core class,
TYPO3\, and only when a
project has explicitly enabled the nesting 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\ | 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\ | Same role, adapted to the TYPO3 13 version of the parent class. |
See List Module Integration for what this XCLASS actually renders and why an event alone was not enough for it.
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) registers['TYPO3_ CONF_ VARS'] ['SYS'] ['form Engine'] ['node Registry'] Wizard\(TYPO3 13 and 14) as theGridelements Backend Layout Wizard Element belayoutwizardFormEngine node, the Grid Wizard's backend rendering, see Grid Wizard. - Context menu item providers
(
$GLOBALS) registers['TYPO3_ CONF_ VARS'] ['BE'] ['Context Menu'] ['Item Providers'] Contextfor the "Paste as Reference" action, see References.Menu\ Item Provider - Scheduler task types and console commands register the data consistency tools described in full at Data Consistency Tools.
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.