Bug #52658: Overriding image does not change the dimensions - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (5)

Christian Ludwig
Dirk Klimpel
Markus Klein
Stefan Neufeind
Thomas Luzat

Actions

Copy link

Bug #52658

closed

Overriding image does not change the dimensions

Added by Claus Harup over 10 years ago. Updated about 10 years ago.

Status:

Rejected

Priority:

Should have

Assignee:

Category:

File Abstraction Layer (FAL)

Target version:

Start date:

2013-10-10

Due date:

% Done:

Estimated time:

TYPO3 Version:

6.1

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

When using the build in file upload functionality and overriding an image, the image gets uploaded, but the width and height in sys_file does not get set properly which leads to that the Frontend uses the old dimensions... :-(

Related issues 5 (0 open — 5 closed)

Related to TYPO3 Core - Bug #44105: Image size does not get updated

Closed

2012-12-19

Actions

Related to TYPO3 Core - Bug #50392: Specifying size in ImageViewHelper does nothing

Closed

2013-07-24

Actions

Related to TYPO3 Core - Bug #62400: Lot of entries in sys_file_processed with name=NULL and identifier empty

Rejected

Andreas Wolf

2014-10-22

Actions

Related to TYPO3 Core - Bug #59216: Image dimensions (width/height) are 0 when not scaled

Closed

2014-05-30

Actions

Related to TYPO3 Core - Bug #61181: FAL: file maxW and maxH are ignored

Rejected

2014-08-25

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Stefan Neufeind over 10 years ago

Could it be you're experiencing problems with different storages being used? We once had a case where the image was updated by upload through the filelist (using auto-created storage 1). But the page-template was using the image via regular paths without specifying a FAL-storage (and thus using the legacy-storage 0). In our case the dimensions were updated correctly in storage 1. This was part of what the patch for "always finding the best-matching storage" (#45498) was planned to address.

Please have a look in the database for your file and what storages/dimensions are listed there.

Actions

Copy link

Updated by Claus Harup over 10 years ago

That is exactly my case!!
Im using an image path in my TypoScript.....

Actions

Copy link

Updated by Stefan Neufeind over 10 years ago

Which version are you using? 6.1.x? According to the dates it should already be part of 6.1.5 (released: 12.9.2013).
https://review.typo3.org/#/c/23560/ (merged for 6.1-branch: 8.9.2013)

Actions

Copy link