Project

General

Profile

Actions

Bug #58952

closed

Inconsistent extension/package relative paths

Added by Chetan Thapliyal over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-05-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #58288: Cache that write absolute paths needs PATH_site in cache identifierClosed2014-04-28

Actions
Actions

Also available in: Atom PDF