Feature #5718
open
Implement File upload support
0%
Description
The RequestBuilder object should handle file uploads as request arguments. A File object is needed to map the params and can be persisted. Reading of the file is done by a file reader extending abstract file reader which can be used to create objects from file data. Validation can be applied to the File object by writing the corresponding FileValidator.
Attached files are a quick try at csv file reading. Usage of property mapper should be rewritten.
Files
Updated by Jochen Rau about 14 years ago
- Status changed from New to Accepted
- Target version set to Extbase 1.3.0beta1
Updated by Sebastian Kurfuerst about 14 years ago
Hey Jochen,
do you know the corresponding implementation of Resources in FLOW3? I think, in case we implement this feature, we should also do it like it is done in FLOW3.
Greets,
Sebastian
Updated by Sebastian Kurfuerst over 13 years ago
- Tracker changed from Feature to Story
- Subject changed from File upload support to Implement File upload support
- Status changed from Accepted to New
Updated by Sebastian Kurfuerst over 13 years ago
- Priority changed from Should have to Could have
- Target version deleted (
Extbase 1.3.0beta1)
Won't have this feature in the near future, if nobody implements it along the lines of FLOW3.
Updated by Thomas Maroschik over 13 years ago
FLOW3 uses a RessourceObjectConverter along with a RessourceManager for this. We could backport this if object converter support in #5595 gets into trunk.
Updated by Sebastian Kurfuerst almost 13 years ago
- Tracker changed from Story to Feature
Updated by Kevin Ulrich Moschallski about 12 years ago
Hi everyone,
is there any update on backporting the FLOW3 ResourceManager to extbase?
Since the new property mapper brought us the FLOW3 type converter in extbase the backport should be possible now, right?
I currently trying to implement a clean way to upload a file or multiple files with a fluid form. I tried it with support of the fed extensions fileObjectStorage in conjunction of the Tx_Fed_Resource_File.
The problem is that Tx_Fed_Resource_File only handles already uploaded files, which leads the to the problem that i can't use it as property type in my model.
So i digger more into this and find this bug, after a quick look into the FLOW3 implementation i think this would be quite nice for extbase.
The biggest problems i think will be:
- Support TCA upload folder instead of a global folder like in FLOW3
- First bring #34528 into master (this will be a breaking change, as all upload properties will change from string to array)
- As far i can see the upload then would take place before validation is passed, this could lead to garbage files
- Maybe FAL should be implemented (don't know much about this up to now)
I really looking forward to hear some opinions on this as i'm willing to implement this or help on it.
Updated by Alexander Schnitzler over 11 years ago
- Status changed from New to On Hold
Set this to 'on hold' because we have to wait until the new property mapper can finally be used securely. This will be done for 6.1.
Updated by Alexander Schnitzler almost 11 years ago
- Status changed from On Hold to New
- Target version set to Extbase 6.2
Updated by Alexander Schnitzler almost 11 years ago
- Status changed from New to Accepted
Updated by Anja Leichsenring almost 11 years ago
- Target version changed from Extbase 6.2 to Extbase 6.3
Updated by Alexander Opitz over 9 years ago
- Project changed from 534 to TYPO3 Core
- Category changed from Extbase: MVC to Extbase
- Status changed from Accepted to New
- Target version changed from Extbase 6.3 to 7.0
Updated by Mathias Schreiber over 9 years ago
- Target version changed from 7.0 to 7.1 (Cleanup)
Updated by Stefan Neufeind over 9 years ago
Helmut created something regarding file-uploads with Extbase and FAL: https://github.com/helhum/upload_example
Updated by Helmut Hummel over 9 years ago
- Status changed from New to Accepted
- Complexity set to hard
Would be great, to have something like that implemented.
However, please be aware, that by providing this solution to a broader audience I learned that it is not optimal like this. The file reference converter should rather respect that it is at the same time a resource as it is a domain model (title, description) etc.
I had no time to implement this as an example yet and most likely will not have the time to do so for 7.1
Updated by Gerrit Code Review about 9 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37898
Updated by Gerrit Code Review about 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37898
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Gerrit Code Review almost 9 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37898
Updated by Gerrit Code Review almost 9 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37898
Updated by Gerrit Code Review almost 9 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37898
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 8 years ago
- Target version changed from 7.5 to 8 LTS
Updated by Wouter Wolters about 8 years ago
- Status changed from Under Review to New
Updated by Riccardo De Contardi about 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Oliver Hader almost 3 years ago
- Related to Bug #93797: error while property mapping a FileReference in frontend added