Bug #63955
closedFatal Error if Ressource could not be found
0%
Description
Hi there
If there is a image in a RTE field which could not be found, i get a fatal error (#1314516809).
The solution should be, that everything else except the image would be parsed.
This is specifically the case, if files with special characters (umlaute) are present.
=> in that case the file path is urlencoded and as such not present in the underlying file system
Anyhow, the parse func should account for that case and
1) urldecode the paths
2) not throw a fatal error, but catch it and ignore the image
Kind regards
Manuel
Updated by Stanislas Rolland almost 10 years ago
When does the error occur? While editing in the RTE or at the time of rendering in the frontend? Where is this fatal error raised?
Updated by Georg Ringer almost 10 years ago
- Status changed from New to Needs Feedback
Updated by Stanislas Rolland almost 10 years ago
I am not able to reproduce this issue with current master. The file name is encoded but the image is rendered.
I am not able to reproduce this issue in TYPO3 CMS 6.2.7 either.
Updated by Stanislas Rolland almost 10 years ago
- Target version deleted (
next-patchlevel)
Updated by Manuel Bloch over 9 years ago
Thanks for your answer.
I can also not reproduce this in the current Master.
How ever, i saw that there are other, related issues to this problem
Updated by Benni Mack over 9 years ago
- Status changed from Needs Feedback to Closed
This is fixed with 7 now. Thanks for the report!