Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Blueprints/FileUploadAPI

From TYPO3Wiki
Jump to: navigation, search

<- Back to blueprints overview

Blueprint: File Upload API

Proposal Create a file uploading API in the TYPO3 Core that can be extended by different implementations to handle file uploads in the TYPO3 Backend (and maybe even Frontend)
Owner/Starter noone yet
Participants/Members -
Status Draft, Discussion, Voting Phase, Accepted, Declined, Withdrawn
Current Progress Unknown, Started, Good Progress, Bad Progress, Stalled, Review Needed
Topic for Gerrit fileupload

Goals / Motivation

There has been a history of "File Uploader" interfaces in the Backend of TYPO3 Core since the early ages. Starting from simple "Upload" Input field, the integration of SWFUploader (in 4.3, removed in 6.1), the addition of the HTML5 "multi-uploading" technique for modern browsers (in 6.0). This is most probably not the end, because the current usability of the uploader is lacking and the techniques available change from time to time.

So the most generic way would be to create a file uploading API in the TYPO3 Core which can be implemented by different extensions to provide uploaders, e.g. PlUpload, SwfUpload, AwesomeUploader, etc. An "upload provider" needs to provide all necessary resources for displaying (markup, javascript) the interface.

The concept should also make sure the API works with Extbase/Fluid. When started, basic research should be done for existing solutions in other Frameworks and in the PHP world (i.e. in TYPO3 Flow, Symfony, etc).

Concept

@todo

Implementation Details

@todo

Risks

The project was kick started on Forge in 2011 (https://forge.typo3.org/projects/typo3v4-fileupload) by Christian Müller, Steffen Kamper, Kay Strobach. Not much happened since. The relevant guys did not had the time to continue working on that and the interest is gone.

So the risk is that this will never happen. But instead of just closing down the project, we wrote down this Blueprint so that someone can catch the ball and work on it.

Issues and reviews

Dependencies upon other Blueprints

External links for clarification of technologies