Project

General

Profile

Actions
Copy link

Bug #19398

closed

callUserFunction and getUserObj uses different object pools

Added by Christian Jul Jensen about 16 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Mathias Schreiber
Category:
-
Target version:
-
Start date:
2008-10-01
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Remote Sprint

Description

Both ways of instantiating an object has the possibility to instantitate the object as (pseudo) singleton by prefixing the classname with &.

But they use different object pools, namely:
$GLOBALS['T3_VAR']['callUserFunction'] and $GLOBALS['T3_VAR']['getUserObj']

This prohibits the use of references to objects across different hooks/callbacks

(issue imported from #M9458)

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Task #77243: Deprecate GeneralUtility::getUserObj()ClosedMathias Brodala2016-07-25

Actions
Actions
Copy link

Also available in: Atom PDF