Tell me about it! Its quite insane that there is no single-standard solution for this. I have been hanging around in #django for sometime and there is still opposition to flash based solution. Also, i have not been to get it working inspite of it being not an ideal solution. I hear that there are some issues with filebrowser since it uses Uploadify. Also, i dont see any solution which works in both dev server and also in the production using httpd/apache.
Going insane! Let me know if you get anything working. PS: As i said, html5 is cool and works, but the client does not want to use it! -V- http://twitter.com/venkasub On Thu, Jun 3, 2010 at 9:54 AM, Brad Pitcher <bradpitc...@gmail.com> wrote: > Sort of, that's what the default is in the demo, but now I've noticed I > have the same problem with apache progress reporting as I did using django > progress reporting. It's behaving like it's not multi-threaded or > something. It seems like I don't get any progress reports until the file > has finished uploading. It's actually driving me a bit crazy so I'm going > to have to move on to something else for a while. > > On Wed, Jun 2, 2010 at 9:16 PM, Venkatraman S <venka...@gmail.com> wrote: > >> Does this work with the Django development server? >> >> >> On Thu, Jun 3, 2010 at 8:13 AM, Brad Pitcher <bradpitc...@gmail.com>wrote: >> >>> Since I just spent much longer than it should have taken figuring this >>> out, I will try and help you out. I followed the instructions at the >>> provided link and it sort of worked. Not quite as well as I liked. I >>> used Apache for the progress reporting, which the author doesn't >>> mention in the article but it is discussed here: >>> >>> http://piotrsarnacki.com/2008/06/18/upload-progress-bar-with-mod_passenger-and-apache/ >>> (it involves compiling and installing an apache module). >>> The author also doesn't mention changes needed in settings.py: >>> from django.conf import global_settings >>> >>> FILE_UPLOAD_HANDLERS = ('path.to.UploadProgressCachedHandler', ) + >>> \ <-- change path here >>> global_settings.FILE_UPLOAD_HANDLERS >>> >>> If you are using nginx or apache for the server side instead of >>> django, you will need to modify progressUrl to point to whatever url >>> you set up for accessing progress reports. >>> >>> If you are looking for a demo, there is one linked in the article >>> creecode posted. >>> -Brad >>> >>> On May 30, 12:23 pm, Venkatraman S <venka...@gmail.com> wrote: >>> > HI creecode, >>> > >>> > Can you share the project please? I can probably work on it and see >>> what is >>> > happening. >>> > Till now, i havent even been able to get this working. >>> > >>> > -V >>> > >>> > On Sun, May 30, 2010 at 10:45 PM, creecode <creec...@gmail.com> wrote: >>> > > Hello V, >>> > >>> > > On May 29, 11:00 pm, Venkatraman S <venka...@gmail.com> wrote: >>> > >>> > > > I have been trying to build a simple file upload with progress bar. >>> > >>> > > AFAIK there isn't a simple solution. Perhaps this info < >>> > >>> > > >>> http://www.fairviewcomputing.com/blog/2008/10/21/ajax-upload-progress... >>> > > > will point you in the right direction. >>> > >>> > > I've experimented with a solution based tthe above but I wasn't >>> > > entirely satisfied with my implementation. I'm having a problem with >>> > > the progress bar not reaching 100% many times and some problems with >>> > > the percentage complete number. >>> > >>> > > I've put my project on the back burner for now but if anyone has any >>> > > examples they'd like to share I'd be interested in seeing them. >>> > >>> > > Toodle-looooooooooo........... >>> > > creecode >>> > >>> > > -- >>> > > You received this message because you are subscribed to the Google >>> Groups >>> > > "Django users" group. >>> > > To post to this group, send email to django-us...@googlegroups.com. >>> > > To unsubscribe from this group, send email to >>> > > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> >>> <django-users%2bunsubscr...@googlegroups.com<django-users%252bunsubscr...@googlegroups.com> >>> > >>> > > . >>> > > For more options, visit this group at >>> > >http://groups.google.com/group/django-users?hl=en. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Django users" group. >>> To post to this group, send email to django-us...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/django-users?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To post to this group, send email to django-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/django-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
