Bug #79290
closed
Fluid cannot override default resolved paths if default paths exist
100%
Description
Since changes in how CMS Fluid sorts template paths were performed, one place in code was not updated.
https://github.com/TYPO3/TYPO3.CMS/blob/master/typo3/sysext/fluid/Classes/View/TemplatePaths.php#L118 contains a loop which array-merges path configurations, but the default paths are added LAST which results in those paths being checked FIRST. This must be changed to append configured paths on top of default paths.
Updated by Gerrit Code Review almost 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51283
Updated by Anonymous almost 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 3135fdc1a6d85e1942edcabe14373de32094db18.
Updated by Nicole Cordes almost 8 years ago
I don't get the problem here but the applied patch is breaking extensions, which set an own path e.g. for module configuration.
This configuration isn't working anymore as it is overwriten by the default paths:
module.tx_example {
view {
templateRootPaths.0 = EXT:example/Resources/Private/Backend/Templates/
partialRootPaths.0 = EXT:example/Resources/Private/Backend/Partials/
layoutRootPaths.0 = EXT:example/Resources/Private/Backend/Layouts/
}
}
Due to the patch the issue popped up. Before the patch everything worked like expected (and was overwriten the right way)!
Updated by Anonymous over 7 years ago
- Related to Bug #81099: Extension cannot override default (fallback) templateRootPaths/partialRootPaths/partialRootPaths added
Updated by