Bug #22029
closed
cropHTML not honoring whole word setting
Added by Ron Hall almost 15 years ago.
Updated about 6 years ago.
Description
First, I want to say I love the new cropHTML stdWrap property. But I have found one bug. It is not honoring the whole word setting. This TypoScript:
10 = TEXT
10.value = <h1>This is my line of text I want to crop</h1>
10.cropHTML = 21 |...| 1
produces this output:
<h1>This is my line of te...</h1>
It should be:
<h1>This is my line of ...</h1>
I have tested on TYPO3 4.3.1
(issue imported from #M13371)
Files
Hi Ron.
Unfortunately, I was not able to reproduce this issue. It may be caused by a (wrong) combination of charsets. cropHTML assumes that the incoming content has the same encoding as the content of the page.
Could you please post your settings
1) $GLOBALS['TSFE']->renderCharset
2) charset of the passed string (coming from a file or the database connection)
Jochen
Hi Jochen,
I think I found the issue. I should have not put a space before the "1" for the whole word setting.
This does not work
10.cropHTML = 21|...| 1
This does work
10.cropHTML = 21|...|1
Thanks for checking on this. I can work with it now. You can close the issue as far as I am concerned.
Hi Ron.
IMO it is a small bug as the expected behavior for options is to behave exactly the same as crop.
Jochen
Committed to SVN TYPO3core
- trunk (revision 7102)
- TYPO3_4-3 (revision 7103)
- Status changed from Resolved to Closed
Also available in: Atom
PDF