Epic #64632
closed
How should FAL handle the upload of (existing) filenames
0%
Description
The attached document describes how filesystems usually handle the upload of files, especially with still existing filenames and how FAL should handle this behaviour.
Files
Updated by Ingo Schmitt almost 10 years ago
- Sprint Focus set to On Location Sprint
Updated by Mathias Schreiber almost 10 years ago
- Tracker changed from Task to Epic
- Status changed from New to Needs Feedback
- Assignee changed from Frans Saris to Andrea Herzog-Kienast
- write down how it should be
- keep limits of browsers and asynchronous communication in mind
Write your findings into the ticket description.
Please do not attach documents.
Images are fine, but please keep them inline to make the ticket more readable.
Updated by Andrea Herzog-Kienast over 9 years ago
FAL should behave like other filesystems:
In Windows Systems it works in the same was as on MAC OS. (See image in attached file from above, I can't add an image inline)
If you try to add the same image again you are asked: Take both / stopp / replase
Take both: filename is extended with „copy“.
So we like to have a box like the MAC Screenshot shows: take both (and extend the filename), stopp (do not upload) , overwrite/replace.
In Case of replace, all referenced files should be replaced.
It is really recommended to set.
Available options shound be configurable via User - TS and overwrite should be a file security option. Direct upload in page module should work in the same way.
Updated by Benni Mack over 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to New
- Priority changed from -- undefined -- to Should have
Updated by
Updated by Mathias Schreiber over 9 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed