Issue Bug Closed

#58952Inconsistent extension/package relative paths

Chetan Thapliyal 05/20/14, 11:06 updated 07/10/14, 18:13

Description

Filesytem structure:

/
www
system-a
system-b
system

Scenario:
web server document root: /www/system
system is a symlink to /www/system-a

If caches are cleared and pages are crawled from CLI, a typo3 extension e.g. news, will have a package object cache containing “/www/system-a/typo3conf/ext/news/” as package path. The PATH_site constant in this case will be /www/system-a/ and package relative path as “typo3conf/ext/news/” (absolute path – PATH_site).

Now if a page is accessed from browser, PATH_site constant will be /www/system/. Extension relative path in this case will be “a/typo3conf/ext/news”. The extra “a/” prefix in the relative path results from the shorter PATH_site string.

I am unable to figure out the right solution to resolve this problem. But I believe storing Typo3 relative paths in package objects should fix the issue.

Comments and suggestions are welcome.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.