Project

General

Profile

Actions

Bug #67625

closed

image width of exactly 85px gets ignored, images get rendered in original size

Added by Thomas Oliver Moll over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Image Cropping
Target version:
-
Start date:
2015-06-19
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hi,

a user showed me a curious case: He uses textpic and sets an image width of 85px. The file he uses has a width of 2400px.
In Backend everything looks fine, but in Frontend the Image is enormous!
When I set 83,84,86,150 or 850px everything looks as expected: the images get rendered in the chosen pixel width.

85px is ok, when I select the backwards-compatibility css-styled-contents 6.1.

I switched of Extensions that might interfere, so the bug seemes to be somewhere in CSS Styled Contens

I would guess there is some kind of condition like if(w<85) / if(w>85) and someone forgot the "==-Case" but I found nothing in the Code.

Unfortunately, i'm not sure if this Bug came with 6.2.13 or if it was present in 6.2.12... but it seems as it arrived with 6.2.13.

Actions #1

Updated by Frans Saris over 9 years ago

  • Status changed from New to Needs Feedback

Try clearing the processed files. That should resolve your issue.

In latest version of 6.2 there is an action in the install tool for this. Else you could truncate the db table sys_file_processfile.

Actions #2

Updated by Thomas Oliver Moll over 9 years ago

that's what I already tried, I used the function in the Upgrade Wizard - no change :-(

Actions #3

Updated by Frans Saris over 9 years ago

Can you reproduce it with a different image?

If not could you check what process file records are present in db for the image with the issue.

Actions #4

Updated by Riccardo De Contardi about 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF