A general file upload field without access to the media manager in core would be indeed great.
I can see a lot of use cases such as the user avatar or like written in the contact form.

+1

A general purpose file upload field isn't practical (even with "normal" forms), there is a lot of extra logic that has to be wired up to process the form submission and specifically the uploads that makes it pretty difficult to create a general purpose solution. File uploads are generally something you need to have something specific to your workflow to use.

in the first line it is me that I get pictures sent. of course it could be other file formats. Why should not that be practical? It always depends on for which purpose this is used. This should then perhaps be selected via a selection field. Which internal networks there must be .. no idea. I ask the question to the professionals. if this is not possible, then that is ok. if the effort is not worth it, then this is also ok.

• thank you - to google for the translation

File inputs are probably the most trickiest of the HTML input types because they require you to write a server side processor for that data specifically. The logic processing the data has to read the file upload data, perform validation rules on it (based on your form's configuration as well as basic security checks), and handle putting it into the filesystem in the desired location. A lot of that upload logic is going to be very specific to a use case, so it's difficult to write a single plugin that just handles all types of file uploads with an unlimited number of constraints/configurations.

The contact form is an even more unique case as if you're looking for the email that gets sent out to have the upload(s) as attachments then the custom field logic has to be able to hook into the email sending logic; there isn't an integration point for that right now.

Not saying that this absolutely cannot be done, but to make a generic upload custom field type takes a lot more planning and consideration than most other field types.

thank you for your information, then I must look for a different solution

+1
Hello, what about Allon Moritz's DPAttachments? Maybe his solution is a possible candidate for a similar core feature? Would be nice to hear some thoughts from master @laoneo ;)

Besides, what about the up-coming new media-manager? Doesn't it have an accompanying media field and more flexible features? For instance: Restrict uploads and formats per field, restrict directories, restrict UI display ... Hopefully a better ACL and fine-grained permissions.

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17936

closed as following the Comment of @mbabker

ACL in media manager needs to be discussed if we really want to got that way as it requires a full blown document manager solution which we have already extensions which are doing it. DPAttachments would also not fit for this use case and I have no plans to migrate that into core as extensions should do jobs like that.

Why is it already closed @franz-wohlkoenig ? @mbabker said also "Not saying that this absolutely cannot be done"
Wouldn't it be good to provide a field from core to prevent others doing it the wrong way? :)

Set to "open" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17936

reopened as stated above.

The problem with such a field is that it requires security checks and heavy server side processing. That processing would be very situational as to what should be allowed and where to store the uploaded files.
This likely needs a component dealing with that.

Imho, we shouldn't add a generic custom field for file upload. This is one of the cases where 3rd party extensions can jump in and provide specialised solutions for the various use cases.

I think this issue should be against the new media manager (NMM) repo.
If media manager is always the component that deals with all the user related files (I guess this is the aim for the NMM) then this could be possible tackled is some way there (I mean beefing up the media field with conjunction to the fields params and the storage adapters).
I can think a way that this could work, but obviously it needs some testing/experimentation etc..

Any news about a Upload File - Custom Field?

Any news about a Upload File - Custom Field?

I've recently attempted to produce a website showcase with Joomla custom fields, where users of a certain component can register and add a description of their live website from the frontend. One of the problems I ran into is that I can't limit an author to see only his/her own homepage screenshot in the media manager.

However, there is a new extension (I didn't test it yet) which might fill the shortcomings of using Joomla custom fields for such custom field applications. See: Field JT Fileupload Currently it is limited to uploading pdf files, but I think it's pretty easy to add more file types.

Any news about a Upload File - Custom Field?

I've recently attempted to produce a website showcase with Joomla custom fields, where users of a certain component can register and present their live website. One of the problems I ran into is that I can't limit an author to see only his/her own homepage screenshot in the media manager.

However, there is a new extension (I didn't test it yet) which might fill the shortcomings of using Joomla custom fields for such custom field applications. See: Field JT Fileupload Currently it is limited to uploading pdf files, but I think it's pretty easy to add more file types.