Project

General

Profile

Actions

Bug #17941

closed

typolinkCheckRootline not working with multiple websites under one umbrella website.

Added by Robert Destigter almost 17 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Communication
Target version:
-
Start date:
2007-12-19
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I am running multiple websites under one root (umbrella) website.

Technically this means that I have a root page containing a TypoScript template and a domain record (sys_domain). The subpages of this root page are actual websites. These pages do not contain TypoScript templates, but do have a domain record.

This setup makes the websites accessable through the root website or directly via their own domain.

The difference with running TYPO3 with multiple websites each having their own root template is that the websites in my setup have to have their own url segment. Otherwise they couldn't be accessable through the root website.

The problem is that the option "typolinkCheckRootline" does not work for this situation. Why? Because $GLOBALS['TSFE']->tmpl->rootLine0 will always be the same for each website.

This makes it impossible to link to a page from another website.

(issue imported from #M7016)


Related issues 5 (0 open5 closed)

Related to TYPO3 Core - Bug #16182: Domain Substitution in external linkClosed2007-07-30

Actions
Related to TYPO3 Core - Bug #15202: links to pages with a different sys_domain recordClosedChristian Kuhn2005-11-15

Actions
Has duplicate TYPO3 Core - Feature #14206: typolinkCheckRootline don't workClosed2004-06-16

Actions
Has duplicate TYPO3 Core - Bug #18432: Linking between domains in the pagetree with checkRootline does not work with menusClosedDmitry Dulepov2008-03-12

Actions
Is duplicate of TYPO3 Core - Bug #16147: Linking between domains in the pagetree ignores simulate static documentsClosedDmitry Dulepov2006-05-15

Actions
Actions #1

Updated by Robert Destigter almost 17 years ago

I'm not in hurry to get this fixed in TYPO3 4.x, but I do think it's an issue that should be considred during the developement of TYPO3 5.0.

I'm not sure if their are any other issues that could come up in a setup as I described.

Actions #2

Updated by Helmut Hummel over 16 years ago

resolved with TYPO3 4.2

Actions

Also available in: Atom PDF