TYPO3 Core

You can solve this by using

<a href="{f:uri.typolink(parameter:link) -> f:format.htmlspecialchars()}" class="xxx">{header}</a>

Any news on this topic?

<a href="{f:uri.typolink(parameter:link) -> f:format.htmlspecialchars()}" class="xxx">{header}</a>

Is no workaround in any case. If the link has already a target, title etc. this would be ignored in this case.

I dont know how to create a patch, so i post code which fixed it for me. I added the following code to TypolinkViewhelper.php at line 150.

if (strpos($typolinkConfiguration['url'], '&')) {
    // Separate additional params from url. uid needs to be in url, so we need to
    $pos = strpos($typolinkConfiguration['url'], '?') + 1;
    $url = substr($typolinkConfiguration['url'], 0, $pos);
    $query = substr($typolinkConfiguration['url'], $pos);
    parse_str($query, $params);
    $typolinkConfiguration['url'] = $url + 'uid=' + $params['uid'];
    unset($params['uid']);
    $typolinkConfiguration['additionalParams'].= '&' . http_build_query($params);
}

It basically looks into the url part of typolinkConfiguration for an ampersand, and if found, adds all additional query parameters to the 'additionalParams' section of the link configuration. Because the uid parameter needs to be part of the url section, the uid is handled separately.
Maybe the more correct place would be the decode function of the TypoLinkCodecService.

Sorry, my code diddnt fix the issue. The class is now appied correctly, but the generated link is not. I think this is because the t3://record?identifier=tx_news&uid=... cannot be resolved if i move the uid in the first place.

The probleme here is that DatabaseRecordLinkHandler ignores any settings from the $conf-array, because it uses the configuration from config.recordLinks.
It should somehow mix the config.recordLinks with the data from $conf, but it seems this is not a trivial task. Its not clear what parameters should be overwritten or appended. $target should be overwritten, but $class could be overwritten or appended. And mixing aTagParams would be a mess.

Hello

A workaround:

<f:link.typolink parameter="123" additionalAttributes="{class:'some-class'}">

additionalAttributes will not be overriden by linkhandler config, but parameter will be.

DANIEL Rémy wrote:

Hello

A workaround:
[...]

additionalAttributes will not be overriden by linkhandler config, but parameter will be.

This is not working. I just tested it to get a class into the link like this:

   <f:link.typolink parameter="{link}" additionalAttributes="{class: 'class', data-test: 'test'}" title="{rondellItem.header}">Test</f:link.typolink>

Links without linkhandler are correct. Links with the linkhandler do not have any class or other attribute. Testet on TYPO3 8.7.13.

Maybe solved with #81620 ? Or am I wrong?

Riccardo De Contardi wrote:

Maybe solved with #81620 ? Or am I wrong?

#81620 solves part of the issue.

But, it remains an edgecase.

TLDR;
always put the page uid directly in the typolink parameter, not in parameter.

Context

- A typolink is make from a Fluid VH : <f:link.typolink parameter="{linkValue}" class="btn btn-small">{linkLabel}</f:link.typolink>
- In the Fluid template, {linkValue} contains t3://record?identifier=rss&uid=416

Not working TS config:

config.recordLinks.rss {
    typolink {
        parameter.data = field:uid
        useCacheHash = 1
    }
}

Working TS config:

config.recordLinks.rss {
    typolink {
        parameter = {field:uid}
        parameter.insertData = 1
        useCacheHash = 1
    }
}

Explanation:

In both cases, DatabaseRecordLinkBuilder receives t3://record?identifier=rss&uid=416 - "btn btn-small" as typolink parameter.
In both cases, DatabaseRecordLinkBuilder builds a typolink configuration (result from a merge of the typolink parameter and the TS config), and call ContentObjectRenderer->typolink function.

But...

In the former, ContentObjectRenderer->typolink receives this:

parameter = - - "btn btn-small" 
parameter.data = field.uid

In the latter, ContentObjectRenderer->typolink receives this:

parameter = {field:uid} - "btn btn-small btn-outline-white" 
parameter.insertData = 1

Conclusion
I don't think this is a bug: with #81620, a typolink configuration is now correctly merged from the Fluid VH to the linkhandler configuration.
But the linkhandler TS config must be very carefully wrote.

Regards.

In specific cases, this bug is still an issue. See https://forge.typo3.org/issues/90404

Patch set 2 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74534

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74576

Patch set 2 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74576

Patch set 3 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74576

Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74620

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74620

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74620

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74620

Patch set 5 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74576

Upgrading to 11.5.11 seems to be breaking the returnLast feature:

link = TEXT
link.typolink.parameter.field = header_link
link.typolink.returnLast = url

header_link contains "https://www.example.org _blank" is my example.

With 11.5.10 the result is https://www.example.org
With 11.5.11 the result is https://www.example.org _blank

Philipp Kitzberger wrote in #note-35:

Upgrading to 11.5.11 seems to be breaking the returnLast feature:
[...]

header_link contains "https://www.example.org _blank" is my example.

With 11.5.10 the result is https://www.example.org
With 11.5.11 the result is https://www.example.org _blank

Hey Philipp,

thanks for this important hint. I will open a new ticket for this