Bug #39904
closed
Unresized image not displayed in FE after move in filelist
Added by internezzo ag almost 12 years ago.
Updated over 6 years ago.
Category:
File Abstraction Layer (FAL)
Description
When an image is moved in the filelist which is used unresized in a content element (CE), the wrong path is used in the FE.
Steps to reproduce:
- Create folder test1 and test2 and upload an image to test1
- Create CE with type image and integrate the image
- Check FE: image is directly linked to fileadmin/user_upload/test1/image.jpg
- Move image to test2 folder in filelist
- Clear cache / reindex FAL with scheduler task
- Check FE: image is still linked to test1 folder --> image is not displayed
- Edit CE: resize image
- Check FE: image is displayed correctly from processed folder
- Move image back and forth: FE remains intact as long as the image is resized
- Status changed from New to Needs Feedback
What I don't get from your description: Did you move the file manually or by using FAL methods? Because the former method might sometimes break stuff, though we have taken some measures to ensure consistency of the file index; the latter should definitely not break anything. Maybe this issue is related to #40033 - we'll have to check that.
I moved the file in the backend module filelist.
Ok. Could you check if the index record in sys_file is updated, i.e. if the identifier of the file is changed to .../test2/...
? This should normally happen, but maybe something is broken here.
Andreas Wolf wrote:
Ok. Could you check if the index record in sys_file is updated, i.e. if the identifier of the file is changed to .../test2/...
? This should normally happen, but maybe something is broken here.
Forget what I said here... I found the reason for this bug: Even for files where no processing is applied (because they don't have to be resized etc.), a ProcessedFile object is created and linked to the content record. This record points to the original location of the file, but is not updated when the file is moved. Thus the relation breaks.
A solution could be to simply not create the ProcessedFile altogether when a file is not changed. I don't know why it happens at all or why there is no check if the file has been processed before creating the record...
- Category set to Frontend
- Status changed from Needs Feedback to Accepted
- Target version set to 6.0 final
- Project changed from 1401 to TYPO3 Core
- Category changed from Frontend to Frontend
- Target version deleted (
6.0 final)
- Category changed from Frontend to File Abstraction Layer (FAL)
- TYPO3 Version set to 6.0
- Status changed from Accepted to Under Review
- Assignee set to Steffen Ritter
- Target version set to 6.0.0-beta2
- Status changed from Under Review to On Hold
processed files handling is completely in rewrite
- Status changed from On Hold to Under Review
- Target version changed from 6.0.0-beta2 to 6.0.0-RC1
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF