Project

General

Profile

Actions

Bug #63955

closed

Fatal Error if Ressource could not be found

Added by Manuel Bloch over 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
RTE (rtehtmlarea + ckeditor)
Target version:
-
Start date:
2014-12-17
Due date:
% Done:

0%

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

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


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #61861: Frontend throws exception on missing imageClosed2014-09-24

Actions
Actions #1

Updated by Stanislas Rolland over 9 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?

Actions #2

Updated by Georg Ringer over 9 years ago

  • Status changed from New to Needs Feedback
Actions #3

Updated by Stanislas Rolland over 9 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.

Actions #4

Updated by Stanislas Rolland over 9 years ago

  • Target version deleted (next-patchlevel)
Actions #5

Updated by Manuel Bloch almost 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

Actions #6

Updated by Benni Mack almost 9 years ago

  • Status changed from Needs Feedback to Closed

This is fixed with 7 now. Thanks for the report!

Actions

Also available in: Atom PDF