Issue Bug Closed

#19398callUserFunction and getUserObj uses different object pools

Christian Jul Jensen 10/01/08, 10:34 updated 05/10/17, 19:47

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)

Reviews 1