// No configuration found
if (!isset($settings['plugin.']['tx_frontendediting.'])) {
$layoutPath = 'EXT:frontend_editing/Resources/Private/Layouts/';
$templatePath = 'EXT:frontend_editing/Resources/Private/Templates/Toolbars/Toolbars.html';
$partialPath = 'EXT:frontend_editing/Resources/Private/Partials/';
} else {
$layoutPath = $settings['plugin.']['tx_frontendediting.']['view.']['layoutRootPath'];
$templatePath = $settings['plugin.']['tx_frontendediting.']['view.']['templateRootPath'];
$partialPath = $settings['plugin.']['tx_frontendediting.']['view.']['partialRootPath'];
}
$view = new \TYPO3\CMS\Fluid\View\StandaloneView();
$view->setTemplatePathAndFilename($templatePath);
$view->setLayoutRootPaths([
10 => $layoutPath
]);
$view->setPartialRootPaths([
10 => $partialPath
]);
Is from the content post processing hook. It depends on legacy naming of templateRootPath as described in #75 but worse than this, it misuses the setTemplatePathAndFilename
- it sets this to a root path rather than a specific filename as is the intended usage.