Issue Bug Closed

#79939ContentObjectRender renders unprocessed href attribute

Malte Koitka 02/21/17, 14:10 updated 10/02/18, 11:02

Description

The ContentObjectRenderer does resolve the new t3:// links correctly. But it also renders the unprocessed/raw href attribute, resulting in two href attributes.

Content in DB:

<a href="t3://page?uid=4">My Link</a>

Content in Frontend:

<a href="index.php?id=4" href="t3://page?uid=4">My Link</a>

Expected content in Frontend:

<a href="index.php?id=4">My Link</a>

Currently this has no negative side effects on rendering, because the DOM simply ignores the second href.

I did have a look into the source: It seems that ATagParams does include “href=“t3://*”. Thus ContentObjectRenderer::typoLink resolves “parameter” and additionally outputs ATagParams. Though I’m not 100% sure where to tackle the root of that problem.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.