Bug #18915
closed
typolink changes a dot in an image filename also to ‚(dot)’
0%
Description
IMO the typolink in the following TypoScript Code does’t work correct:
-----
temp = COA
temp.1 = IMAGE
temp.1 {
file = fileadmin/img/icons/email.gif
stdWrap.typolink {
parameter = anfrage@domain.de
}
}
plugin.tt_news {
displayList {
email_stdWrap.cObject < temp.1
}
}
-----
For the tt_news marker ###NEWS_EMAIL### in the displayList function ‚temp.1.stdWrap.typolink’ generates the following HTML-code:
-----
<a href="javascript:linkTo_UnCryptMailto(...);"><img src="fileadmin/img/icons/email(dot)gif" width="14" height="10" border="0" alt="" title="" /></a>
-----
The dot in the filename „fileadmin/img/icons/email.gif“ was also changed to „(dot)“, and so, the image can’t found.
This problem i have post in many forums but up today i cann't solve it. It's the first time i report here an i hope you can understand my english.
(issue imported from #M8628)
Updated by Georg Ringer over 16 years ago
i tested this at a 4.2. and it works fine there.
can anyone test it on a 4.0 to confirm?
Updated by Johannes C over 16 years ago
Just in time, i have got a tip about spam config. In my configuration, the property 'spamProtectEmailAddresses_lastDotSubst' was set to '(dot)'. After delete it, the dot in the image filename is fix and will no longer be replaced.
But now, the dot in the E-Mail Adresses will not substitute. The output is 'name(at)domain.com'.
Updated by Oliver Hader over 16 years ago
@Johannes: That's correct. There was a bug which was fixed in the TYPO3 4.1 branch, but not for 4.0.x. So, you could upgrade to the most recent TYPO3 version (4.2) or patch your source manually by the related bugs mentioned with this issue.
Updated by Oliver Hader over 16 years ago
Please report if you still experience the problem with TYPO3 4.1.7 or TYPO3 4.2.1.
You can find the pre-releases at http://translation.typo3.org/temp_packages/ (release planned for June 9 2008)
Updated by Christian Kuhn over 15 years ago
Resolved, no change required:
- There was no feedback for a long time as requested.
- This is probably solved in recent versions.
Please reopen if this problem still exists.
Updated by