.Shortcuts symlinks use absolute path
The symlinks in the .Shortcuts folder use absolute paths. This is an issue in chrooted environments where the path to the document root can be a different one then the path in the webserver process.
This causes the symlinks to be working in only one situation: during CLI execution or during a HTTP request, depending on which generated the symlink.
Updated by Bernhard Fischer almost 9 years ago
The symlinks in the Web/_Resources/Static/Packages folder should also follow relative pathnames for an chrooted installation. Otherwise a cache warmup on CLI will lead to non-existing pathnames.
The usage of relative symlink creation should be done in general on non Windows systems. This also regards the PrivateResourcesPublishingAspect class, which uses absolute symlinks as well.
The unit test for Utilitys/Files.php still fails. I'd assume directory symlink removal is done by unlink() but it has to be done by rmdir() even if it is a symlink.