Add section about Template naming and locations to PAGEVIEW #1546
+36
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I just try to get PAGEVIEW running and get errors like: Tried resolving a template file for controller action "Default->Pages/Default" in format ".html", but none of the paths contained the expected template file (Default/Pages/Default.html). That's why I would prefer to provide a running example in first section, before we start explaining the containing variables for Fluid templating.
fe-hicking
reviewed
Mar 15, 2025
|
|
||
| **Template Naming Convention**: | ||
|
|
||
| * The Fluid template file should match the name of the selected backend layout |
There was a problem hiding this comment.
Should we drop a word about the misleading term "backend layout" here and mention it's really more a "page layout"? :-)
There was a problem hiding this comment.
We have these messages all over and everyone is still confused. It should be changed in the core.
Co-authored-by: Garvin Hicking <[email protected]>
|
Thanks, that is a good improvement. In would however suggest to also improve the error messages in the Core about this. Edit: see here: https://review.typo3.org/c/Packages/TYPO3.CMS/+/88597 |
linawolf
approved these changes
Mar 15, 2025
|
I added a commit suggesting some changes, expecilly I would use headlines as they can be linked when needed. Also this is not really part of the example above |
linawolf
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I just try to get PAGEVIEW running and get errors like:
Tried resolving a template file for controller action "Default->Pages/Default" in format ".html", but none of the paths contained the expected template file (Default/Pages/Default.html).
That's why I would prefer to provide a running example in first section, before we start explaining the containing variables for Fluid templating.