Bug #64539
closed
Module view paths configuration has no effect
Added by Stanislas Rolland almost 10 years ago.
Updated almost 9 years ago.
Description
Setting module view paths in TypoScript has no effect.
For example,
module.tx_myextension {
view {
templateRootPath = EXT:myextension/Resources/Private/Backend/Templates/
partialRootPath = EXT:myextension/Resources/Private/Backend/Partials/
layoutRootPath = EXT:myextension/Resources/Private/Backend/Layouts/
}
}
has no effect. Extbase always looks for templates in the default paths.
This is a regression from TYPO3 6.2.
- Is Regression changed from No to Yes
- Status changed from New to Needs Feedback
- Assignee set to Anja Leichsenring
Hey Anja,
got an idea what's going on?
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version deleted (
7.5)
I just tried to find the right configuration for the extensions generated by the the ExtensionBuilder:
For an extension with extensionkey beonly and a submodule key backendmodule under mainmodule web these typoscript settings work with 7.5:
modules.tx_beonly.view.templateRootPaths.0
or
modules.tx_beonly_web_beonlybackendmodule.view.templateRootPaths.0
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Anja Leichsenring)
I think that this could be closed; please look at: https://docs.typo3.org/typo3cms/extensions/core/latest/Changelog/7.0/Breaking-62673-ExtbaseDeprecatedCodeRemoved.html
ActionController
Support for old view configuration options templateRootPath, layoutRootPath and partialRootPath is dropped. Use the new options with fallback mechanism.
Moreover there has been no activity since the last 90 days.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Thank you
Also available in: Atom
PDF