Project

General

Profile

Actions

Bug #25317

closed

Typolink fails to link between two non-default page types

Added by Franz G. Jahn over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2011-03-14
Due date:
% Done:

0%

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

Description

If you try to link from a page type with typeNum != 0 to another page type using typolink the parameter notation pageId,typeNum described in tsref (http://typo3.org/documentation/document-library/core-documentation/doc_core_tsref/4.3.2/view/1/5/#id2507605), the link will contain the current type as well.

Steps to reproduce:
Take an environment with three different page types (e.g. default (type=0), print version (type=98), plaintext (type=42)).
Create a text contet element containing three link-tags (assuming pageID=23):
<LINK 23,0>test normal</LINK>
<LINK 23,98>test print</LINK>
<LINK 23,42>test plaintext</LINK>

Now, if you take a look on the output of the plaintext type, the generated links will look as follows:
http://example.com/index.php?id=23&type=98&type=42

Addionally, type=0 won't be considered at all.

Solution:
t3lib_tstemplate::linkData should consider type parameter during "uniqueLinkVars"-Handling

Additionally, $typeNum should not be considered as a boolean variable. It should be checked, whethere is $typeNum contains an integer or not.

Improvement: After exploding the link parameters, it should be checked whether type is explicitiy set to "0". If the parameters contain type=0, the type parameter can be left out.

Proposed patch appended. Problem seems to affect all TYPO3 Versions

(issue imported from #M17937)


Files

patch-typolink.diff (1.69 KB) patch-typolink.diff Administrator Admin, 2011-03-14 14:24
Actions

Also available in: Atom PDF