Project

General

Profile

Actions

Bug #44557

closed

Filelist Navframe Errorcode

Added by Benjamin Einert over 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2013-01-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.0
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After Upgrade from Typo3 4.5 the filelist tree is not working.
I get an Link to the Errorcode "file name is invalid" -> http://typo3.org/go/exception/v4/1320288991


Files

typo3_backend_php.jpg (26.3 KB) typo3_backend_php.jpg Benjamin Einert, 2013-01-15 22:29
Actions #1

Updated by Jigal van Hemert over 11 years ago

  • Category set to Backend User Interface
  • Status changed from New to Needs Feedback
  • Priority changed from -- undefined -- to Should have

Can you check in your fileadmin directory if there are directories / files with a very strange name? The exception occurs if after cleaning up invalid characters and dots no name is left.

Actions #2

Updated by Benjamin Einert over 11 years ago

Sorry, but I can't find any strange file or entry in fileadmin.
I even moved everything out there but the error still remains.

Where else should i search for such a file?

Inserting an image in an content element I get the Error:

Oops, an error occurred!
File //.depdb is not valid (".." and "//" is not allowed in path).
More information regarding this error might be available online.

This seems there is such a strange filename but i can't find it so far.

Actions #3

Updated by Reasken Kurz about 11 years ago

Are there any news about this issue? I can reproduce the same problem which is shown in the attached image by Benjamin.

There are no directories/files with strange or empty names in my fileadmin either.

Actions #4

Updated by Alexander Opitz over 10 years ago

Hi,

does this issue persist in newer versions of TYPO3 CMS (6.1)?

Actions #5

Updated by Markus Klein over 10 years ago

  • Is Regression set to No

Is this still an issue on 6.0 or 6.1?

Actions #6

Updated by Alexander Opitz about 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

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.

Actions #7

Updated by Andrea Herzog-Kienast over 8 years ago

Same issue while updating from 4.7.x to 6.2.15
Problem was a file with wrong characters. The system changed the character to __ (double undercore) and i changed it into ae. This solved the problem.

Actions

Also available in: Atom PDF