Install tool marking symlinked directories as errors.
I am trying a 6.1.7 -> 6.2.0 upgrade and I noticed that the install tool is marking symlinked directories as errors that need to be corrected.
To me this is not an error as symlinks to directories are not errors that need to be corrected. I often symlink entire document roots to quickly switch served content.
I would suggest that if a symlink is detected that the symlink target is followed (using PHP readlink) and then verified. Of course a target can have a different name than it's link, so that would need to be taken in consideration. As long as the link has the correct naming there should be no problems.
Anything can be logically symlinked in a hosting environment for all manner of perfectly valid reasons. They should not be marked as errors unless they are truly broken links. (i.e. the target doesn't exist)
A symlink in itself is not an automatic error without further investigation.
Updated by Christian Kuhn almost 7 years ago
The first patches for this issue did not go far enough and had to be reverted:
There are several different scenarios the install tool should cope with. This should be allowed on configuration level:
- example typo3_src: This is usually a link to a directory, but it may be a directory as well.
- example index.php: This is usually a link to a file, but it may also be a file directly, too. The content of the file should have a defined content.
- example fileadmin: This is usually a directory, but it may be a link pointing to a directory as well.
I propose to have a deeper look at the folderStructure DefaultFactory default structure definition and to align on a structural change of the configuration that allows these kind of configuration.
Hint: Since the folder structure can not be extended by extensions, we're relatively free to change this.