Issue Bug Under Review Stale

#93409Inconsistent parsing of URLs without <a> tag

Sybille Peters 02/02/21, 10:48 updated 09/10/26, 21:54

Description

Parsing of URLs without a <a href tag in tt_content.bodytext gets inconsistent results.

Sometimes it is a link in the frontend, sometimes not, the rendering of frontend and RTE is not always consistent.

Example 1

<p>Weitere Informationen sind auf der Webseite des Projekts zu finden https://www.klasse-klima.de/.<br />
BUNDjugend, Klasse Klima (https://www.klasse-klima.de/sfsd)<br />
</p>
  • In the frontend, the first URL is rendered as link, the second is not
  • In the RTE, both links are not rendered as links

Example 2

URL without <a href and directly followed by a “)” gets different results:

1. is rendered as link in frontend
2. is not rendered as link in RTE
3. is incorrectly evaluated by linkvalidator as URL with the ), so e.g. URL “https://example.org” becomes “https://example.org)”

tt_content.bodytext has softref:

typolink_tag,email[subst],url

I have wondered about the “url” in there, if you remove that you could just parse explicit links with ““ as links which seems to me to be a “cleaner” solution.

Example

The following (raw) example text in tt_content.bodytext:

<p>(some url http://t3coredev/sdfdsf2) more text ...</p>

system

  • latest master
  • with Introduction package
  • points 2 and 3 can be reproduced without Introduction Package, did not test 1) as that requires rendering of content in frontend

Reviews 1

History 34

  1. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2025-04-03T13:32:21+00:00" > 04/03/25, 13:32 </span>

    I think that this is still reproducible with the latest main (14.0.0-dev) and CKEditor5:

    if you type

    (https://www.google.com)

    it is not automatically converted into a link; to convert it you have to add a space before and after the parenthesis – thus you have to “isolate” the link (let me pass the term), e.g.:

    ( https://www.google.com ) 

    It looks like this is a behavior of CKEditor, as I can reproduce it on the editor online demo https://ckeditor.com/docs/ckeditor5/latest/examples/builds/classic-editor.html

    I admit I have not tested the behavior of the linkvalidator