#50788Fluid Content Object does not configure object manager
Description
If some TS defines “register implementation” like:
config.tx_extbase {
objects {
# Register ‘fx’ as default namespace and allow if condition string comparison
TYPO3\CMS\Fluid\Core\Parser\TemplateParser {
className = Enet\FxLibrary\Core\Parser\TemplateParser
}
}
}
Then, this class “override” is not done if a Fluid template content object is rendered. The reason for this is, that usually extbase Bootstrap.php method “configureObjectManager” takes care of looping through “objects” framework definition and pushed registered implementations to the object manager. But this bootstrap is NOT done in fluid content object context.
Possible solution: probably “copy” the method “configureObjectManager” from extabse bootstrap to ext:frontend FluidTemplateContentObject?!
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.