Issue Bug Closed

#10947514.2: using plugins on the page level results in exception

Dmitry Dulepov 04/02/26, 17:09 updated 04/17/26, 18:49

Description

This is new in TYPO3 14.2.

Given:

page.10 < plugin.tx_myext_pi1

results in:

(1/1) #1725892141 TYPO3\CMS\Core\Domain\Exception\RecordPropertyNotFoundException
Record property "header" is not available.

This happens because ExtensionUtility::configurePlugin(() sets this TS:

tt_content.' . $pluginSignature . ' =< lib.contentElement

Now lib.contentElement makes this:

lib.contentElement {
    dataProcessing {
        1770716912 = record-transformation
    }
}

Since the plugin is inserted on the page level, the record is the instance of \TYPO3\CMS\Core\Domain\Page. Then it goes to the fluid styled content rendering, which includes “Header” partial, which searches for the header field, which is obviously not in the page record. The result is the exception.

Since it is quite common to set up plugins on the page level, this needs to work as before.

Reviews 1