Feature #5718

Implement File upload support

Added by Alexandre Martinez over 3 years ago. Updated 18 days ago.

Status:Accepted Start date:2009-12-11
Priority:Could have Due date:
Assignee:- % Done:

0%
Category:Extbase: MVC
Target version:Extbase 6.2
Has patch:No Tags:
Votes: 8 (View)

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.

RequestBuilder.php (2.9 kB) Alexandre Martinez, 2009-12-11 14:21

File.php (4.1 kB) Alexandre Martinez, 2009-12-11 14:21

AbstractFileReader.php (2.6 kB) Alexandre Martinez, 2009-12-11 14:21

CsvFileReader.php (2 kB) Alexandre Martinez, 2009-12-11 14:21

History

#1
Updated by Jochen Rau about 3 years ago

  • Status changed from New to Accepted
  • Target version set to Extbase 1.3.0beta1

#2
Updated by Sebastian Kurfuerst about 3 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

#3
Updated by Sebastian Kurfuerst over 2 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

#4
Updated by Sebastian Kurfuerst over 2 years ago

  • Category set to Extbase: MVC

#5
Updated by Sebastian Kurfuerst over 2 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.

#6
Updated by Thomas Maroschik over 2 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.

#7
Updated by Sebastian Kurfuerst almost 2 years ago

  • Tracker changed from Story to Feature

#8
Updated by Kevin Ulrich Moschallski about 1 year 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.

#9
Updated by Alexander Schnitzler 6 months ago

  • Status changed from New to On Hold
  • Has patch set to No

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.

#10
Updated by Alexander Schnitzler 26 days ago

  • Status changed from On Hold to New
  • Target version set to Extbase 6.2

#11
Updated by Alexander Schnitzler 18 days ago

  • Status changed from New to Accepted

Also available in: Atom PDF