Bug #45696
closed
typo3 crashes (with exeption) if a Image is deleted in fileadmin
Added by Christian Tauscher over 11 years ago. Updated over 8 years ago.
0%
Description
If you delete a image in fileadmin via ftp, the Error "File has been deleted." is trown.
This is true, and not a Bug at all (...as designed...) but I think this design is a bug.
It should still render the rest of the Content, without the image.
Stopping to work is not accepted by normal editors - they even dont understand this behavior.
Thank you,
Christian.
Files
| t3-error.jpg (121 KB) t3-error.jpg | Christian Tauscher, 2013-03-25 16:37 |
Updated by Andreas Wolf over 11 years ago
- Category set to File Abstraction Layer (FAL)
Updated by Dmitry Dulepov over 11 years ago
- Status changed from New to Needs Feedback
I just tried that: it shows empty image. There is no crash.
What do you mean by "crash"? Could you post error messages or attach screnshots?
Updated by Christian Tauscher over 11 years ago
Dont delete this via fileadmin.
Delete or move the file via ftp.
TYPO3 does not track this change:
Uncaught TYPO3 Exception
#1329821485: File has been deleted. (More information)
RuntimeException thrown in file
/var/www/htdocs/typo3_src-6.0.1/typo3/sysext/core/Classes/Resource/AbstractFile.php in line 492.
30 TYPO3\CMS\Core\Resource\AbstractFile::getPublicUrl()
.....
If you need the whole crash-report, let me know.
Thank you for taking care of this.
Updated by Stefan Galinski over 11 years ago
- Status changed from Needs Feedback to Accepted
How to reproduce (in master):
- create an image/text element and add an image
- remove/move the referenced image
- open the page in the frontend --> crash on first call
Updated by Benni Mack over 11 years ago
- Status changed from Accepted to Needs Feedback
There is no error in the backend nor in the frontend with the latest master. Can you still reproduce?
Updated by Christian Tauscher over 11 years ago
- File t3-error.jpg t3-error.jpg added
Yes I still can reproduce this.
You have to be logged into the BE.
if you are not logged in then no error is given, but the rendering of the FE is wrong:
The missing image is rendered with wrong width/height.
Seems this values are taken from the database, the original-images sizes.
The given screenshot shows:
the row with images. Sould be 4 lines with each 3 pics in it.
the forst image was deleted.
look at the firebug output:
image fileadmin/editor/PSO011.jpg is missing, but the dimensions are the original images dimensions.
The with sould be "91px", see secound image opened.
hope this helps,
Christian.
Updated by Jigal van Hemert over 11 years ago
- Status changed from Needs Feedback to New
Updated by Sebastian Fischer over 10 years ago
Well the "should be" part i cant agree on. If the image is not available on the resizing should be done on some dimension. Unless the image gets processed there are no new dimensions to add in the img tag. Thats why it gets rendered in "full" size.
Beside that is not what the issues is about originaly. If the size is a problem, please file a new issues with descriptive subject.
Updated by Alexander Opitz about 9 years ago
- Status changed from New to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.15 or 7.6.0)?
Updated by Riccardo De Contardi almost 9 years ago
I think it has been solved with #71686; I have performed the following little test:
1) upload a file /fileadmin/photo_02.jpg
2) create an HTML file /fileadmin/Layouts/Default.html:
<f:render section="content" />
3) create an HTML file /fileadmin/Templates/Default.html:
<f:layout name="Default" />
<f:section name="content">
<div id="content">
<f:image src="fileadmin/photo_02.jpg" />
</div>
</f:section>
4) TS setup:
page=PAGE
page.10 = FLUIDTEMPLATE
page.10 {
templateName = Default
layoutRootPaths {
10 = fileadmin/Layouts
}
partialRootPaths {
10 = fileadmin/Partials
}
templateRootPaths {
10 = fileadmin/Templates
}
}
if I remove the image outside from TYPO3 (e.g. directly from the filesysyem), I obtain an empty img tag <img />
Updated by Andreas Allacher almost 9 years ago
There are multiple ways to show images, therefore in other cases it might still crash which is why it would be good to know how exactly the image is rendered, e.g. I think IMAGE / IMG_RESOURCE might still throw an exception.
Updated by Riccardo De Contardi almost 9 years ago
page.20=IMAGE page.20.file=fileadmin/test0.jpg
As far as I can see, if I delete the image, the whole <img> tag is not rendered (same with IMG_LAYOUT)
Updated by Riccardo De Contardi over 8 years ago
- Status changed from Needs Feedback to Closed
The bug described in the ticket seems solved, so I think I can close this safely; moreover there has been no feedback within the last 90 days.
If there is still a way a missing image could break the frontend because an exception comes through there should be a new ticket with a suitable description.
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.
Thank you