Epic #64570
Updated by Ingo Schmitt over 9 years ago
Some time ago I realized, that the file system type (case in/sensitive) is set during a TYPO3 installation, which can cause serious troubles if you setup the system on a case insensitive fs, such as the ones of Windows and Mac.
This is a unnecessary pitfall because most websites are served by unix servers, that are case sensitive. So instead of silently detecting and setting the fs option during the installation we should go for strong defaults and a new installation step.
During the installation we could check for a case insensitive file system and warn the user that the default is case sensitive, but with the option to change that during the development phase with a hint to the consequences if one forgets to change that after the deployment.
Additionaly the reports module should be enhanced to show if the current fs matches the fs option of FAL and warn the user.
We have to consider these topics:
*General*
* Changing the filename / directory name from upper case to lower case (and vise versa) on no case sensitive Filesystems (#25180)