Actions
Bug #19398
closed
callUserFunction and getUserObj uses different object pools
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)
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Franz Holzinger over 11 years ago
The methods callUserFunction and getUserObj
have been moved into the file typo3/sysext/core/Classes/Utility/GeneralUtility.php.
The problem remains the same.
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to New
Updated by Mathias Schreiber almost 10 years ago
- Assignee set to Mathias Schreiber
- Target version set to 7.1 (Cleanup)
- Is Regression set to No
- Sprint Focus set to Remote Sprint
Updated by Benni Mack over 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Benni Mack over 7 years ago
- Status changed from New to Closed
Fixed in master, as the SingletonInterface is in place for this.
Actions