Project

General

Profile

Actions

Bug #22029

closed

cropHTML not honoring whole word setting

Added by Ron Hall almost 15 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Communication
Target version:
-
Start date:
2010-01-30
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

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

issue_13371_v1.diff (810 Bytes) issue_13371_v1.diff Administrator Admin, 2010-02-11 17:18
Actions #1

Updated by Jochen Rau almost 15 years ago

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

Actions #2

Updated by Ron Hall almost 15 years ago

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.

Actions #3

Updated by Jochen Rau almost 15 years ago

Hi Ron.

IMO it is a small bug as the expected behavior for options is to behave exactly the same as crop.

Jochen

Actions #4

Updated by Jochen Rau over 14 years ago

Committed to SVN TYPO3core
- trunk (revision 7102)
- TYPO3_4-3 (revision 7103)

Actions #5

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF