Project

General

Profile

Actions

Bug #24977

closed

Extension using stdWrap hooks are broken due to stdWrap refactoring

Added by Jo Hasenau almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
Start date:
2011-02-07
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

There is a discussion about an extension in the dev list, that implements the interface: http://typo3.org/extensions/repository/view/ogonki/current/info/class.tx_ogonki_hook.php/

the problem in above case is that the $configuration variable is not read anymore...

function stdWrapProcess($content, array $configuration, tslib_cObj &$parentObject) {
debug($configuration);
return $content;
}

in debug it returns only an array:

stdWrapProcess 1
stdWrapProcess.

no more $configuration['glueOrphans'] is available, although it's in TS.

This is true for other extensions using these hooks.

The problem is in the way how tslib_content handles the $conf Array. It is intersected with an array of availabl stdWrap functions and then handed over to these functions.

This should not be the case with any stdWrap hook and actually it was intended to hand over the original $conf array to these functions, which unfortunately doesn't happen with the current code.

Attached is a solution that replaces as check for the non existant value "stdWrapHookObjects" with a check for the function type "hook".
(issue imported from #M17507)


Files

17507.diff (611 Bytes) 17507.diff Administrator Admin, 2011-02-07 21:30

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #23688: Replace the current if-construct of stdWrap with real functions and make each of them stdWrap awareClosedSteffen Kamper2010-10-07

Actions
Actions

Also available in: Atom PDF