Bug #20672

Using typolinkLinkAccessRestrictedPages does not take different domain names into account

Added by Oliver Hader over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Communication
Target version:
-
Start date:
2009-06-25
Due date:
% Done:

0%

TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Imagine the following page structure:

+--- Page 1 (id:1), on domainA.com
|     |
|     +--- Page 2 (id:2), only accessible for logged in users
|
+--- Page 3 (id:3), on domainB.com

The TypoScript settings are the following:

config {
  typolinkLinkAccessRestrictedPages = 1
  typolinkLinkAccessRestrictedPages_addParams = &redirect=###PAGE_ID###
}

If I now set a link on Page 3 to Page 2, I'll get the following link:

http://domainB.com/index.php?id=1&redirect=2

However, the expected behaviour would be, that the domain name of Page 1 is used:

http://domainA.com/index.php?id=1&redirect=2

(issue imported from #M11412)

0011412.patch View (994 Bytes) Administrator Admin, 2009-06-25 16:13

History

#1 Updated by Oliver Hader over 10 years ago

The attached patch reprocesses the page with typolink again...

#2 Updated by Oliver Hader over 10 years ago

Committed to SVN:
  • TYPO3_4-2 (rev. 5698)
  • Trunk (rev. 5699)

Also available in: Atom PDF