Bug #57036
closed
Standalone Fluid does not consider extbase config
0%
Description
Fluid StandaloneView does not consider framework configuration.
Example:
config.tx_extbase.objects {
TYPO3\CMS\Fluid\ViewHelpers\DebugViewHelper.className = TYPO3\CMS\Fluid\ViewHelpers\CommentViewHelper
}
Furthermore it would make sense to have this also on cObject level.
10 = FLUIDTEMPLATE
10.extbase.objects {
TYPO3\CMS\Fluid\ViewHelpers\DebugViewHelper.className = TYPO3\CMS\Fluid\ViewHelpers\CommentViewHelper
}
Updated by Helmut Hummel about 10 years ago
Markus Klein wrote:
Fluid StandaloneView does not consider framework configuration.
Makes sense.
Furthermore it would make sense to have this also on cObject level.
I would refrain from implementing this
Updated by Markus Klein about 10 years ago
Furthermore it would make sense to have this also on cObject level.
Was suggested by MaBa. ;-)
Updated by Marc Bastian Heinrichs about 10 years ago
Markus Klein wrote:
Furthermore it would make sense to have this also on cObject level.
Was suggested by MaBa. ;-)
jep, my though was, if you have in on plugin or module level, you should have it also on standalone level.
But could be problematic with nested FLUIDTEMPLATE objects... not simple to implement... caching foo...
Updated by Claus Due over 8 years ago
- Status changed from Accepted to Closed
Let's continue this one in the other issue; #50788 - if the fault still applies, it's going to be fixed there. I agree with Helmut that this should be at the current low level it is; not replicated in cObject. The trick would be to make our non-Extbase usage contexts correctly bootstrap Extbase framework configuration (as mentioned in linked issue).