Project

General

Profile

Actions

Bug #63954

closed

typolink_URL ignores forceAbsoluteUrl

Added by Andreas Moeller over 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-12-17
Due date:
% Done:

0%

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

Description

Hi,
I am using the following code segmet:

$conf = array(
            'parameter' => $GLOBALS['TSFE']->id,
            'forceAbsoluteUrl' => 1,
        );

        $link = $this->cObj->typolink_URL($conf);

My result is a relative URL such as: /de/test
Of course that is wrong. My result should look like this: http://www.test.de/de/test

By the way. When i use the function typolink() instead of typolink_URL() everything works fine.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #65666: typolink, typolinkEnableLinksAcrossDomains and forceAbsoluteUrl strips absRefPrefixClosedMarkus Klein2015-03-11

Actions
Actions #1

Updated by Steffen Müller over 9 years ago

  • Project changed from 1865 to TYPO3 Core
  • Category deleted (Configuration)
  • Is Regression set to No
Actions #2

Updated by Mathias Brodala over 9 years ago

I occasionally experience the same issue with the Extbase UriBuilder which internally uses mentioned ContentObjectRenderer::typoLink_URL method.

Actions #3

Updated by Frederic Gaus about 9 years ago

I tested this on 6.2 and on current master but I'm not able to reproduce this. Could you please provide more information of you configuration?

Actions #4

Updated by Markus Klein about 9 years ago

Please test this without realurl!

If you see a difference in typolink_URL() and typolink(), then there is most likely a hook in
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['typoLink_PostProc']
which does some stuff.

Actions #5

Updated by Frederic Gaus almost 9 years ago

  • Status changed from New to Closed

This issue could not be reproduced. Also, no feedback for 5 month. This is why I close this issue. If you think this was the wrong decision and you think this but is issue is still valid, please open a new ticket with a relation to this one.

Actions

Also available in: Atom PDF