Task #50796
closed
Prevent creating a FAL storage that is a subfolder of another storage
Added by Marc Bastian Heinrichs almost 11 years ago.
Updated over 4 years ago.
Category:
File Abstraction Layer (FAL)
Description
Having a FAL storage that is a subfolder of another storage, results in very strange behaviours, especially for editors. e.g.:
id:path
1:fileadmin/
2:fileadmin/projectname/
I would suggest to prevent creating a FAL storage that is a subfolder of another storage.
- Status changed from New to Accepted
- Assignee set to Andreas Wolf
- Target version set to 6.2.0
Yep, should definitely be tackled.
- Status changed from Accepted to On Hold
- Assignee changed from Andreas Wolf to Marc Bastian Heinrichs
Will test it with steffens fixes. Should work...
MaBa: any feedback on this?
- Status changed from On Hold to Needs Feedback
- Target version deleted (
6.2.0)
What is the state of this issue?
6 month later, again the question, what is the state of this issue?
- Status changed from Needs Feedback to Accepted
- TYPO3 Version changed from 6.1 to 6.2
Ok, tested. It's still possible to create nested storages. This will result in dupes in sys_file: multiple records for the same file with different storages.
IMO would be really hard to refactor the filelist and resources api to avoid this in code instead of simple preventing to create nested storages.
- Related to Feature #80523: Action "replace file" in nested File Storage leads to missing file references added
- Status changed from Accepted to Closed
As this is a technical task with nothing happening for a long time, I'm going to close the issue now. If you continue working on it (or restart working on it) please reopen the ticket.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by