Project

General

Profile

Actions

Bug #79680

closed

lib.parseFunc not treating mailto:, tel: etc. links properly

Added by Gregor Favre almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
-- undefined --
Assignee:
-
Category:
Content Rendering
Target version:
-
Start date:
2017-02-08
Due date:
% Done:

0%

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

Description

When using mailto: links in text/media content elements, in the frontend those links are not rendered by lib.parseFunc: the A-tag is removed. However, when not using lib.parseFunc (or removing lib.parseFunc.tags.a), then t3:// links are not rendered. This ends up in either t3:// links not working, or default protocol:// links not working.

Reproduce:
1. Create page with one content element, containing a mailto-Link
2. Assign content element via typoscript as a template variable to fluid template
3a. Render content in fluid template with <f:format.html parseFuncTSPath="lib.parseFunc">{content}</f:format.html>
3b. mailto: Links are not rendered

4a. Render content in fluid template with <f:format.html parseFuncTSPath="">{content}</f:format.html>
4b. mailto: Links are rendered, but all other links (i.e. pagelinks) are not rendered

TYPO3-Version: 8.5.1
Using fluid_styled_content

Actions #1

Updated by Gregor Favre almost 8 years ago

  • Category set to Content Rendering
Actions #2

Updated by Gregor Favre almost 8 years ago

  • Priority changed from Must have to -- undefined --

I cannot reproduce the behaviour above anymore. The links are now working as expected when using the HTML Viewhelper with and without lib.parseFunc.

Whatever the problem was, it was not caching related (all caches deleted, even typo3temp). Also, it doesn't seem to be file related, since we don't see any suspicious changes on GIT in our project. I'd suggest to close this entry but let it remain just in case anyone encounters something similar, who can provide more information.

Actions #3

Updated by Riccardo De Contardi over 7 years ago

  • Status changed from New to Closed

I guess it is safe to close this one for now.

If you think that this is the wrong decision or experience the issue again then please reopen this issue or open a new issue with a reference to this one. Thank you!

Actions

Also available in: Atom PDF