New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Framework for asynchronous file uploads, separate from form submissions (Trac #4712) #4712
Comments
ewinslow wrote on 42534994-09-02 This would be great to figure out. Merits some research into how others solved this problem. |
ewinslow wrote on 42535211-09-28 Design doc: https://docs.google.com/a/elgg.org/document/d/1zW3VoKu1oujtmUGZk6f5GlH3g3ayYSD1xyrmpePKDpo/edit# |
i am researching better upload methods currently.. since i am unable to upload large files to my site via this slow connection - unless i have a resume capability.. plus there are so many other benefits to having a decent upload process. i found that this page contains a great summary of some of the best that already exist: |
I added an API section that moves this along quite a bit (I hope). |
We forked https://github.com/hypeJunction/hypeDropzone by @hypeJunction and created the ability to (seamlessly) replace all input/file with an async version. https://github.com/coldtrick/hypeDropzone |
Original ticket http://trac.elgg.org/ticket/4712 on 42534154-11-21 by trac user mrclay, assigned to unknown.
Elgg version: 1.8
Many users prefer progressive/slicker file upload widgets. These require an asychronous model of handling the form submission, with uploads sent in separate requests than the rest of the form content.
It would be nice to have a pseudo-framework for allowing uploads to arrive ahead of the form, perhaps making it easy to "convert" sync forms with uploads to async.
Of course this opens up lots of questions: What happens if the upload fails? user abandons the form? are any events/hooks triggered? support re-sending a different file? Can we learn from any existing 3rd party plugins that handle this elegantly?
The text was updated successfully, but these errors were encountered: