Feature #66727
closed
- Category changed from Fluid to Extbase
Moved to Extbase since the DebuggerUtility (used by f:debug) is part of Extbase, not Fluid. Any patch to allow this should be made available there rather than only in Fluid's ViewHelper.
$originalResource is not lazyloaded in the usual sense you are used to in extbase. In the case of a lazy annotation it would already show a "LazyLoadingProxy" in the var_dump, which makes it much clearer.
$originalResource is initially "null" and only gets its actual value assigned, the first time its getter getOriginalResources() is called.
This makes it really hard to debug the value in the DebuggeryUtility, because internally, the DebuggerUtility ignores any getter methods and access the properties directly via the Reflection API.
To fix this, one would either:
- have the change the code of TYPO3\CMS\Extbase\Domain\Model\AbstractFileFolder (possibly breaking things)
- or make DebuggerUtility in this specific case call the getter method instead of directly accessing the property. (Then DebuggerUtility would have to "know" about the implementation of a FileReference, which is bad design).
- Status changed from New to Closed
Hello,
thank you for reporting that issue.
Calling each getter of an object may produce heavy load. To prevent that, TYPO3 just shows the property values of given object.
I prefer using
<f:debug>{file.originalResource}</f:debug>
instead of just
<f:debug>{file}</f:debug>
That solution will show you the real content
I will close the ticket now. If you feel this is the wrong decision, let me know, and I will re-open it.
Stefan
Also available in: Atom
PDF