Bug #58952: Inconsistent extension/package relative paths - Core - TYPO3 Forge

Core Indexed Search Linkvalidator Release Cycles Team Resources Workspaces & Versioning TYPO3 CMS Usability Team Community Extensions Distributions Feature-Requests TYPO3 6.2 Projects (+)(Archived Projects)

Bug #58952

Inconsistent extension/package relative paths

Added by Chetan Thapliyal about 1 year ago. Updated about 1 year ago.

Status:

Closed

Start date:

2014-05-20

Priority:

Should have

Due date:

Assigned To:

% Done:

Category:

Spent time:

Target version:

TYPO3 Version:

6.2

Is Regression:

PHP Version:

Sprint Focus:

Complexity:

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.

Related issues