Bug #54344
Broken paths for links created below Web/_Resources/Static/Packages/
| Status: | Closed | Start date: | 2013-12-11 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
When using PHP in a chroot environment (php-fpm + chroot) the „detected“ absolute paths don't match the paths seen by the webserver when serving static assets.
Pre-Requisites:
1) The following directory holds the TYPO3 Neos 1.0 installation: /srv/customers/webs/user1/html/domain1.de/
2) The apache vhost ist configured with a document root: /srv/customers/webs/user1/html/domain1.de/Web/
3) PHP is chrooted to: /srv/customers/webs/user1/
What happens is that Neos/Flow publishes the static resources and creates absolute symlinks pointing to /html/domain1.de/.../, for example TYPO3.Flow -> /html/domain1.de/Packages/Framework/TYPO3.Flow/Resources/Public
These links are correct from the viewpoint of the PHP client but are wrong from the viewpoint of the Webserver. The correct symlink should be relative so that both PHP and Apache can reach the right destination independent of their starting point.
TYPO3.Flow -> ../../../../Packages/Framework/TYPO3.Flow/Resources/Public
History
#1 Updated by Tanel Põld over 1 year ago
It becomes a problem as well if changing the page root in server.
#2 Updated by Jonas Renggli 10 months ago
- Status changed from New to Closed
Thanks for your bug report.
This sound like a TYPO3 Flow issue.
Moved to Jira: https://jira.typo3.org/browse/FLOW-81