Issue Bug Closed

#42963preProcess() hook invoking in some extensions in PageLayoutViewDrawItemHook fails

Frank Gerards 11/14/12, 12:40 updated 01/09/15, 12:44

Description

I noticed, that at least in two extension in my test system (FLUX and tx_damttcontent) there were errors in the page module display in the backend,
that had the same structure:

<myextensionhookclass>::preProcess() must be compatible with that of TYPO3\CMS\Backend\View\PageLayoutViewDrawItemHookInterface::preProcess()…</myextensionhookclass>

I looked into both extension hook classes and found the parameters be the same and are matching the interfaces’ declaration:

Extensions preProcess() parameters: tx_cms_layout &$parentObject, &$drawItem, &$headerContent, &$itemContent, array &$row
Core Interface Class requirements: \TYPO3\CMS\Backend\View\PageLayoutView &$parentObject, &$drawItem, &$headerContent, &$itemContent, array &$row

the tx_cms_layout object type is also mapped on the right namespace path.

Can anybody investigate, why this error occurs although the preProcess-functions in the extensions have the right declaration ?

I consider this a major issue for all extensions that hook into the backend page module.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.