#93983Integrator support: Handling of incorrect filename for typoscript setups
Description
Of course, one can argue/discuss about this. I’ll just take up the problem.
Context: The TypoScript setup was not loaded because the file was called “Setup.typoscript”. In the core itself, of course, the search is for “setup.typoscript”, which is in accordance with the guidelines.
For me, however, there would be potential here to support the integrator. We could also check for a ucwords(‘setup’) file existence and add a log entry if this file exists. For me it’s a low hangin’ fruit.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 2
-
Martin Kutschker commented 06/03/21, 08:34
-
Georg Ringer commented and changed status
NewClosed 10/16/26, 15:59I suggest to close this issue as “won’t fix”.
File names are part of the conventions the core relies on,
setup.typoscriptandconstants.typoscriptare looked up by their exact name. A file with a different spelling likeSetup.typoscriptis simply not the file the core is looking for, and making sure that integrator-provided files follow the naming conventions is the task of the integrator. It works on case-insensitive file systems and fails on case-sensitive ones, which is a deployment problem and not something the core should guess around.Besides that, supporting alternative spellings would require an additional file system lookup just to catch typos, as already noted in the comment.
Yet another file system hit just for the sake of catching typos.
The BE has already some tools that check the instance and extensions. Better to add warnings/hint there.