Bug #29599
closedLinks set on images get a whitespace at the end
0%
Description
Hi there,
when setting a link on an image with T3 4.5.2 there is a trailing whitespace in the link.
This might be a problem for w3.org validation and for some extensions like naw_securedl that do not recognize files that have to be secured when linked with images.
I didn't figure out, why the link is set like this but I'm sure the core team will be able to handle this :)
Greets
Tizian
Updated by Helmut Hummel about 13 years ago
- Status changed from New to Needs Feedback
How do you set the link to the image? In the link wizard of e.g. the header tt_content field, or in the link wizard of the RTE or by using plain TypoScript?
Updated by Helmut Hummel about 13 years ago
There is indeed a whitespace before the closing > but not between the quotes.
<a href="fileadmin/1.jpg" >Image</a>
But how could this be a problem?
Updated by Anonymous about 13 years ago
Hello Helmut,
I set the links in the media tab on the pictures themselves.
Thinking about it, I use DAM but I don't think this interfers in the generation of links on pictures at this point or may I be wrong?
I'll sure check it and give you feedback.
Greets Tizian
Updated by Helmut Hummel about 13 years ago
Tizian Schmidlin wrote:
I set the links in the media tab on the pictures themselves.
Thinking about it, I use DAM but I don't think this interfers in the generation of links on pictures at this point or may I be wrong?
I cannot reproduce it on a plain installation, so I suppose it is a DAM issue.
I'll sure check it and give you feedback.
Thanks!
Updated by Anonymous about 13 years ago
Hello Helmut,
I tested now on an other installation of ours using DAM and it seems that this is not a TYPO3 or a DAM problem, there is probably something else that adds the trailing whitespace.
I'll continue to try to figure out what it could be and post it .
Greets
Tizian
Updated by Chris topher about 13 years ago
- Target version changed from 4.6.0 to 4.6.1
Updated by Chris topher almost 13 years ago
- Target version changed from 4.6.1 to 4.6.2
Updated by Alexander Opitz over 11 years ago
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Tizian Schmidlin over 11 years ago
Seems that this problem does not exist in 4.5.27 anymore.
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to Closed