TYPO3 Core

Hi!

Can you please describe how you enter those links? Are you using the link wizard?

Hi, yes, I am using the link wizard, internal link -> select my page -> click on the little arrow -> choose a content element on the local page.

When I instead edit the links in RTE source view and save it, RTE changes this

<a href="#c123">

to this:

<a href="http://domain.tld/#293&quot;>

which doesn't help, either.

Well, in DB it does not store an a-tag but the custom <LINK ...> syntax. (At least in CMS 7 and lower)
So it does not matter what is shown to you in RTE.
It solely depends on your Template (TypoScript) how the links are rendered in FE, but by default a page is prefixed.

In your manual case the domain is prefixed in FE, due to your absRefPrefix.

What is your actual goal you want to achieve? I propose to get in touch with us on Slack to have direct support.

I'm not talking about what is shown in RTE, I'm looking at the generated source code. I need this functionality for creating pages I want to send out as HTML email newsletters (direct_mail, but it doesn't matter). That means, images need to have absolute paths, as do external links, but local links (anchors) absolutely can not.

If I simply remove the absrefPrefix, images lose their absolute path and can't be loaded from the server. In the past, all local anchor prefix could be controlled with config.prefixLocalAnchors = 0 but this has no effect anymore. I think this is an issue that potentially affects everybody who wants to create email newsletters with TYPO3.

https://typo3.org/community-support/
https://forger.typo3.org/slack

Thanks for explaining the usecase. I have to look up the code changes of the past.

I think this functionality has been removed. There's a related issue btw, prefixLocalAnchors has been moved to compatibility6, but it doesn't work with the extension installed, either. Edit: I have investigated the code and compatibility6 is not supposed to, or going to bring back "local" local anchor functionality.

added relation to
https://forge.typo3.org/issues/62723
https://forge.typo3.org/issues/65934

I performed the following test with the latest master:

1) TS Setup:

config.absRefPrefix = /
config.prefixLocalAnchors >
config.baseURL >

2) I added a link named "totop" using the "flag" icon in CKEditor.

Result¶

<a href="/index.php?id=1&amp;L=0" id="totop" name="totop">Test</a>

Riccardo De Contardi wrote:

I performed the following test with the latest master:

Not sure how this helps, that's not a local anchor (should begin with # as shown), and you won't be able to load images from the server with absRefPrefix = /

Ok sorry I performed a different test on 7.6.20; please note that I use the standard RTE configuration; I just added as page TSConfig:

RTE.default.showButtons = *

I added a text with media content element and then a link to a content element; results:

on RTE:

<p>Lorem Ipsum <a href="http://typo3.7.test.it:8888/?id=18#37" class="internal-link" title="Opens internal link in current window">Dolor</a> Sit Amet</p>

on frontend:

<p>Lorem Ipsum <a href="index.php?id=18&amp;L=0#c37" title="Opens internal link in current window" class="internal-link">Dolor</a> Sit Amet</p>

Now that two people have the same problem, maybe that creates enough pressure to have this fixed.
Local anchors are in the HTML standard, and a trivial matter. I would write the anchors by hand, but the RTE "fixes" them. Possible solutions:

- not use RTE
- don't use local anchors
- don't use TYPO3

None of which fix the problem. We have since (it's been over 1 year) moved to Mailchimp.

It was a joke. Sorry.

In both TYPO3 8.7.20-dev and 9.5.1-dev, local anchors can be set in two different ways:

- first by choosing "internal link" and selecting a content-Element on the current site
- second by choosing "external link" and typing "#ID" into url-field, where ID is the uid of the content-element.

Both links will be rendered the same in FE:

- either "domain/index.php?id=1#c3" (8 LTS)
- or "domain/#c3" (9 LTS)

Both are valid and if there are no other use-cases, the ticket should be closed, I think.