Bug #63955
Fatal Error if Ressource could not be found
| Status: | Closed | Start date: | 2014-12-17 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | rtehtmlarea | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | 5.3 | Sprint Focus: | ||
| Complexity: |
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
History
#1 Updated by Stanislas Rolland 8 months 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?
#2 Updated by Georg Ringer 8 months ago
- Status changed from New to Needs Feedback
#3 Updated by Stanislas Rolland 7 months 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.
#4 Updated by Stanislas Rolland 7 months ago
- Target version deleted (
next-patchlevel)
#5 Updated by Manuel Bloch 2 months 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
#6 Updated by Benjamin Mack 17 days ago
- Status changed from Needs Feedback to Closed
This is fixed with 7 now. Thanks for the report!