Bug #79939
closed
ContentObjectRender renders unprocessed href attribute
0%
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.
Updated by Benni Mack almost 8 years ago
Hey Malte,
maybe you can check if this patch solves your problem: https://review.typo3.org/#/c/51076/
Updated by Malte Koitka almost 8 years ago
Hi Benny! Also with the patch applied, the problem still exists. ContentObjectRenderer::getATagParams does return the unprocessed href, though it shouldn't I guess.
I don't know where exactly it's added in the TYPO3 core rendering or in which place it is safe to delete/exclude the t3-URNs from ATagParams.
Updated by Wouter Wolters over 7 years ago
- Status changed from New to Resolved
Fixed with https://review.typo3.org/#/c/52323/ today