Bug #34351
Uncaught Exception on renamin a folder with subfolder
| Status: | Accepted | Start date: | 2012-02-27 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Andreas Wolf | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 6.0 beta 2 | |||
| Votes: | 0 |
Description
When renaming a folder "test" with a subfolder "subtest" to "test2" an uncaught exception is shown:
#1330119453: Copying file "/test/subtest/" to "/test2/subtest/" failed
The folder renaming is actually successful.
Related issues
| related to File Abstraction Layer - Task #36528: File: Rework property update process | Accepted | 2012-04-24 |
History
Updated by Andreas Wolf about 1 year ago
- Status changed from New to Needs Feedback
- Assignee set to Susanne Moog
This should have been fixed in the meantime. Susi, could you check if it is still relevant?
Updated by Susanne Moog about 1 year ago
- Status changed from Needs Feedback to New
- Assignee changed from Susanne Moog to Andreas Wolf
I can still reproduce it.
- 1: Directory "Images" was not renamed! Write-permission problem in "Images123"?
Filelist module, left frame, context menu > rename
folder structure:
fileadmin
- Images
-- subfolder1
-- subfolder2
-- subfolder3
- Templates
Updated by Andreas Wolf about 1 year ago
- Status changed from New to Accepted
As far as I tracked down, this error comes from non-indexed files, where loading the index record fails. This could be circumvented by catching the exception in t3lib_file_File::updateProperties().
The underlying problem is that the whole "update stuff after moving files" process is still rather messy and not well documented or tested. For now, I'm going to commit the try/catch solution, but we clearly have to optimize this.
Updated by Ingmar Schlecht about 1 year ago
- Target version set to 6.0 beta1
Updated by Steffen Ritter 9 months ago
- Target version changed from 6.0 beta1 to 6.0 beta 2