Bug #63375
StandaloneView must require upperCase file names for Partials and Layouts
Status: | Rejected | Start date: | 2014-11-27 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Anja Leichsenring | % Done: | 0% |
|
Category: | Fluid | Spent time: | - | |
Target version: | - | |||
TYPO3 Version: | 7 | Is Regression: | No | |
PHP Version: | Sprint Focus: | |||
Complexity: |
Description
In order to ensure the convention of uppercased filenames is met, a check for the casing of those files is added.
Related issues
History
#1 Updated by Gerrit Code Review 8 months 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 http://review.typo3.org/34708
#2 Updated by Henrik Ziegenhain 8 months ago
Is this also in 6.2.7 now?!
After updating from 6.2.5 to 6.2.7 I get the following exception:
Uncaught TYPO3 Exception #1288092556: Could not load partial file. Tried following paths: "/www/htdocs/hosting/fileadmin/templates/layouts/Default.html", "/www/htdocs/hosting/fileadmin/templates/layouts/Default".
#3 Updated by Thomas Diedenhoven 8 months ago
I can reproduce the problem too (update from 6.2.6 to 6.2.7). I patched it temporary by commenting out the lines $actionName = ucfirst($actionName) in TYPO3\CMS\Fluid\View\TemplateView.php
#4 Updated by André Spindler 8 months ago
I can confirm this regression. But: "In order to ensure the convention of uppercased filenames is met" - where is this requirement defined - for integrators?
Templating is mainly done by integrators. IMHO there should be suggestions, but not requirements for then. For extension developers I support such requirements.
#5 Updated by Benjamin Mack 8 months ago
- Status changed from Under Review to Rejected
we will not ensure any casing for template files except the templates constructed from the action name.